RE: [gentoo-user] gnu-screen split region can't invoke shell

2022-03-01 Thread Laurence Perkins
Note also that “regions” aren’t actually full children of sessions.  If you set 
up a bunch of regions in a session in one terminal, and then attach to that 
same session in a different terminal, the only evidence of the regions will be 
the odd sizes of some of the windows.  So you can have the same screen session 
attached from different places with different region layouts simultaneously.

LMP

From: russian sky 
Sent: Tuesday, March 1, 2022 5:21 AM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gnu-screen split region can't invoke shell

> 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.

After rereading the info(gnu-screen) manual, which indeed clarifies that

'Ctrl-a S' will generate a blank window.

It works after following your advice, thanks



The gnu-screen runs a litte bit different from tmux which make me

confusing. Good thing is the structure

(sessions --->>> regions --->>> windows) becomes clear, thanks again


Re: [gentoo-user] gnu-screen split region can't invoke shell

2022-03-01 Thread russian sky
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.


After rereading the info(gnu-screen) manual, which indeed clarifies that

'Ctrl-a S' will generate a blank window.

It works after following your advice, thanks


The gnu-screen runs a litte bit different from tmux which make me

confusing. Good thing is the structure

(sessions --->>> regions --->>> windows) becomes clear, thanks again


Re: [gentoo-user] gnu-screen split region can't invoke shell

2022-03-01 Thread Michael
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.


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