On Monday, 28 February 2022 11:12:01 GMT russian sky wrote:
>   Is it a bug that the gnu screen itself can't invoke
> 
> a shell automatically after running 'Ctrl-a S' ?

As far as I know you need to use 'Ctrl-a n' to move the screen focus into the 
next region of the split screen and then 'Ctrl-a c' to start a window in this 
split region with a shell in it.  Otherwise it remains empty.

You could also use 'Ctrl-a 0' to display the content of the first region of the 
screen in the second split region - mirroring what the first region shows.

'Ctrl-a tab' switches focus between regions.  'Ctrl-a n' switches the 
displayed window within a region to the next window which has an active shell 
in it, within the screen session.  Instead of 'n' for next, or 'p' for 
previous, you can enter the number of the window, with 0 being the first window 
in the screen session.

I'm not sure if I explained it an understandable way, but I think with a bit 
of experimentation you'll soon understand how screen sessions, windows with 
shells and split regions work.

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to