Discussion:
"server-info", the "not useful" part
Csaba Henk
2015-01-02 01:44:23 UTC
Permalink
Hi,

the server-info command as it was known in 1.8 has gone
for good in commit 1.9~2^2~18:

http://sourceforge.net/p/tmux/tmux-code/ci/d23561f

The functionality was partly moved to show-messages,
partly discontinued because of being "not useful".

However, there was one thing among the dropped features
I rather liked and used frequently -- the hierarchical
view of sessions/windows/panes.

1) Is there a way to get that data now by some (probably scripted)
means?

2) If not, is there a way to do what I mainly used it for,
that is, to find out in which session/window/pane is a certain
process running (via the associated tty which is shown for the
process by ps(1) and was included in server-info output).

Thanks
Csaba
Nicholas Marriott
2015-01-05 16:44:09 UTC
Permalink
pane_tty and client_tty formats are probably what you want

-------- Original message --------
From: Csaba Henk <***@lowlife.hu>
Date:02/01/2015 01:44 (GMT+00:00)
To: tmux-***@lists.sourceforge.net
Subject: "server-info", the "not useful" part

Hi,

the server-info command as it was known in 1.8 has gone
for good in commit 1.9~2^2~18:

http://sourceforge.net/p/tmux/tmux-code/ci/d23561f

The functionality was partly moved to show-messages,
partly discontinued because of being "not useful".

However, there was one thing among the dropped features
I rather liked and used frequently -- the hierarchical
view of sessions/windows/panes.

1) Is there a way to get that data now by some (probably scripted)
means?

2) If not, is there a way to do what I mainly used it for,
that is, to find out in which session/window/pane is a certain
process running (via the associated tty which is shown for the
process by ps(1) and was included in server-info output).

Thanks
Csaba
Csaba Henk
2015-01-12 00:05:10 UTC
Permalink
Hi Nicholas,
Post by Nicholas Marriott
pane_tty and client_tty formats are probably what you want
Thanks for the pointer, this allowed me to serve as a good pointer
for further research, and thus I found out how to get what I need
via the "list-*" commands.

Csaba

Loading...