Replies: 2 comments
-
Hello @tmjbios, could you tell me more about your connections. See the image here for terminology I refer to: are each terminal window, via ssh, to the same server, using
Running locally one tmux server and two different sessions, the PWD segment seems to show the right directory although sometimes flimmer a bit showing some other directory. Sorry I don't know how to improve this. The relevant code is: tmux-powerline/lib/tmux_adapter.sh Lines 17 to 19 in 887ed21 |
Beta Was this translation helpful? Give feedback.
-
One server, two sessions. Running I'll poke around a bit and see if I can see what the get_tmux_cwd() is doing. Thanks for the reply! |
Beta Was this translation helpful? Give feedback.
-
Hi everyone.
My use case is 3-6 or more open gnome-terminals, all connecting to a single remote machine via ssh over a spotty VPN connection. I'm trying to use tmux-powerline to alleviate losing all my in-progress work when the VPN goes down.
However, the updates tmux-powerline puts out for the segments across the bottom are global; the pwd information for the current active gnome-terminal is reflected in all other windows running tmux. Same for the git branch, etc. Hit in a window 1, and all the other window's segments update to reflect the state of window 1 instead of keeping their data so I can track what window is in which dir, etc.
Is there a quick way to force the updates to be local to a session instead of global across all tmux processes? I've searched the 6+ pages of issues, and I'm not seeing anything describing what I see.
I usually start tmux with just "tmux" when I log in, but starting new sessions with -s doesn't help either. Am I missing something?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions