Hijacking this for a question I've been wondering about. For context, I'm a long-time tmux user who spends 90% of my time in remote shells.
Ideally, I'd have my WM handle panes, layouts, etc. "Terminal multiplexing" seems to me to be misplacing client/UI concerns. Session persistence is the concern of the server, and multiplexing should be handled by ssh. However, getting the client terminals to coordinate nicely (e.g. reattaching to the appropriate sessions, opening new terminals in the same remote working directory) require more sophisticated clients than exist currently (to my knowledge).
Does anyone feel similarly? Anyone have a setup that approximates what I'm looking for?
I'm using resurrect tmux plugin configured to rerun ssh commands, it's not perfect as it's not restoring remote session, but at least you have session open to right host in pane that you expect with scroll history.
Ideally, I'd have my WM handle panes, layouts, etc. "Terminal multiplexing" seems to me to be misplacing client/UI concerns. Session persistence is the concern of the server, and multiplexing should be handled by ssh. However, getting the client terminals to coordinate nicely (e.g. reattaching to the appropriate sessions, opening new terminals in the same remote working directory) require more sophisticated clients than exist currently (to my knowledge).
Does anyone feel similarly? Anyone have a setup that approximates what I'm looking for?