Re: window vs pane

2010-02-26 Thread Trent W. Buck
[I'm playing catch-up in the archives again...] Nicholas Marriott writes: > On Wed, Feb 10, 2010 at 03:01:18PM -0800, Robin Lee Powell wrote: >> A friend of mine has "per-pane status lines" as a requirement before >> he starts using tmux; then you could title each pane appropriately. >> Been mea

Re: window vs pane

2010-02-10 Thread Nicholas Marriott
On Wed, Feb 10, 2010 at 03:31:02PM -0800, Robin Lee Powell wrote: > On Wed, Feb 10, 2010 at 11:25:20PM +, Nicholas Marriott wrote: > > I don't really know what "per-pane status lines" means, although I > > don't use panes so it probably wouldn't help me at all. > > A status line below each pan

Re: window vs pane

2010-02-10 Thread Robin Lee Powell
On Wed, Feb 10, 2010 at 11:25:20PM +, Nicholas Marriott wrote: > I don't really know what "per-pane status lines" means, although I > don't use panes so it probably wouldn't help me at all. A status line below each pane, just for that pane. > Panes don't have names themselves. This would req

Re: window vs pane

2010-02-10 Thread Nicholas Marriott
I don't really know what "per-pane status lines" means, although I don't use panes so it probably wouldn't help me at all. #T is per-pane, as is #P, of course. And automatic-rename uses the pty in the active pane. Panes don't have names themselves. I don't see a huge need for them to have them an

Re: window vs pane

2010-02-10 Thread Robin Lee Powell
On Wed, Feb 10, 2010 at 10:56:47PM +, Nicholas Marriott wrote: > My biggest problem at the moment is remembering which window has > which man page/log file/code/etc open, but so far I haven't > thought of anything that would make that much easier. A friend of mine has "per-pane status lines" a

Re: window vs pane

2010-02-10 Thread Nicholas Marriott
If you are interested in it from a code rather than a user perspective there is another element called a winlink which sits between a session and its windows. It is what allows a window to be attached to many sessions. On Wed, Feb 10, 2010 at 10:45:56PM +, Nicholas Marriott wrote: > Exactly r

Re: window vs pane

2010-02-10 Thread Nicholas Marriott
On Wed, Feb 10, 2010 at 02:38:35PM -0800, Robin Lee Powell wrote: > On Wed, Feb 10, 2010 at 02:36:17PM -0800, Hibiki Kanzaki wrote: > > I am trying to come up with a mental model for all the entities > > (terminal, client, server, session, window, pane). > > > > It seems like for me it might be si

Re: window vs pane

2010-02-10 Thread Nicholas Marriott
Exactly right. A server contains one or more sessions, each of which contains one or more windows, each of which contains one or more panes. A target (used with -t) is a 3-tuple represented as session:window.pane. The server is specified with -L (or sometimes -S) on the command line, servers do

Re: window vs pane

2010-02-10 Thread Robin Lee Powell
On Wed, Feb 10, 2010 at 02:36:17PM -0800, Hibiki Kanzaki wrote: > I am trying to come up with a mental model for all the entities > (terminal, client, server, session, window, pane). > > It seems like for me it might be simplest to imagine that > conceptually it is always a pane that is closest to

window vs pane

2010-02-10 Thread Hibiki Kanzaki
I am trying to come up with a mental model for all the entities (terminal, client, server, session, window, pane). It seems like for me it might be simplest to imagine that conceptually it is always a pane that is closest to the program I see inside a window/pane, even a window with only one pane.