screen - 2 important commands are missing

[netnomad]

2 important screen commands are missing:

C-a \    closes all open screen windows and exit
C-a |    splits the current region horizontally, opposite to C-a S that splits it vertically

the first command makes it so easy to leave screen, also when i work with many open windows.
the second one is useful when i have no windows manager and i work in reduced, basic environments f.e. in an embedded router os... it helps to use, watch and compare different regions from left to right.
perhaps there are different versions of screen and this in the repository has a reduced set of commands?
i proofed that it has nothing to do with the keyboard layout. both characters \ and | are fully functionally.

[netnomad]

hi friends,

is there no one who uses screen out there?
these two commands are so handy that it's hard to believe that no one needs them!?
give them a try.

thank you for your interest.

[bmarkus]

hi friends,

is there no one who uses screen out there?
these two commands are so handy that it's hard to believe that no one needs them!?
give them a try.

thank you for your interest.

Which commands?

[gerald_clark]

I use tmux.

[netnomad]

hi friends,

is there no one who uses screen out there?
these two commands are so handy that it's hard to believe that no one needs them!?
give them a try.

thank you for your interest.

Which commands?

please, read my first, initial post.

[bmarkus]

Looks keyboard issue.

[netnomad]

i proofed that it has nothing to do with the keyboard layout. both characters \ and | are fully functionally.

as far i could check it has nothing to do with the keyboard layout:
in the screen window i could write both characters:  \ and | ,


so i see there no reason why the shortcut-combination:

C-a \    closes all open screen windows and exit
C-a |    splits the current region horizontally, opposite to C-a S that splits it vertically

shouldn't work with my keyboard layout.

thank you for your contributions.

[tinypoodle]

the second one is useful when i have no windows manager and i work in reduced, basic environments f.e. in an embedded router os...

Are you referring to screen running on different OS accessing from core or screen running on core?

[netnomad]

this behavior i can reproduce immediately
when i start screen in a local aterm-window in tinycore-linux.

[bmarkus]

What happenes when you are accessing screen running on TC via SSH from a different system or trying locally with not aterm but another terminal, like lxterminal or any other based on vte?

[netnomad]

i tried it with lxterminal and vte as a dependency: same result!

[althalus]

Horizontal split is ctrl a S. Vertical split was only implemented as an extra patch when I built the screen extension, and I chose not to include the patch.

If you really want force quit, add the following to your .screenrc:

Code: [Select]

bind ^\ quit(this will actually bind C-a C-\, which is what you'll find on any cheatsheet online. If you really wanted C-a \, change ^\ to \\)

On the other hand, force quitting every open window in screen sounds like a monumentally bad idea anyway.

[netnomad]

hi althalus,

thank you for your help and reply.
for the reason i'm used to this behavior in debian,
i included your "bind \\ quit" in my .screenrc and everything works as expected.
i like this command and i see there no problem, because i'm asked for a confirmation before the windows get closed.

i think this vertical split is handy:
it provides almost something like a windows-manager-environment in a single terminal.
i would really appreciate, if you want to consider that patch in your next packaging

thank you for your commitment to tinycore.

[althalus]

i think this vertical split is handy:
it provides almost something like a windows-manager-environment in a single terminal.
i would really appreciate, if you want to consider that patch in your next packaging

Handy, yes, but on the machine I was using at the time, it caused performance problems, so I didn't include it.

I'll add repackaging screen to my to-do list, but can't say when I'll get around to it. Feel free to try yourself if you don't want to wait, or experiment with tmux, as it does a somewhat similar job to screen.

[bmarkus]

I use tmux.

Thanks for mentioning tmux. I disn't know it. As a heavy screen user, will give it a try. It is specially interesting on the raspberry Pi where I have issues witrh screen.