Hell, tmux doesn't need X/Wayland running or anything other than shell - if you can get to a prompt, it can be there.Īs much as I love tiling window managers, I rarely use their actual tiling functionality anymore. Had multiple sessions going and you need them all back with immediacy? Create a script in advance for each session that recreates each, then a parent script that launches them all. Keeping a simple shell script up to date for each desired tmux session allows you to boot up, log in, launch a single term, execute one script, and instantly have a freshly-recreated tmux session with multiple "tabs" (windows) and "splits" (panes), each sized and laid out in prearranged fashion, with the necessary files open in each. In tmux's case, you can mitigate this risk with either a little elbow grease or plugins - it's quite scriptable. Lastly, in situations where you would achieve similar window/pane arrangements in tmux via a tiling window manager with several desktops/workspaces and terms (or a few terms with several splits/tabs), you run the very real risk of having to manually set everything back up again from scratch when power is lost. This is the one area where GNU Screen still excels, but its bugs and instability remove it as a contemporary contender. There are risks, but it's powerful and fast. Tmux likewise empowers shell-level pair programming if you're willing to share ssh access to the same host. You can copy something into its buffer while at work, drive home, and it's still there for pasting. Tmux also has cluster-ssh functionality, which some other programs offer, but while you can integrate its clipboard with your local system's clipboard as well, its own clipboard is persistent from the perspective of where it runs. If you get dropped, you reconnect to VPN, re-ssh, re-attach to tmux session X, and drive on. Even the worst hotel wifi is mostly tolerable if you can get your work done via a single ssh connection to a remote system running tmux. Both tmux and VNC help with persistence when network stability is poor, but the heavier VNC connection (even though it's also over ssh) would feel more sluggish, and get dropped more frequently in extreme low network bandwidth scenarios. The key difference there is that tmux is MUCH more performant then rendering a whole desktop. Being able to reattach to a tmux session from elsewhere (including remotely) is definitely a nice-to-have, though the same could arguably be achieved with VNC. This is its most traditional use case, as was the same for GNU Screen, its predecessor. Long-running processes benefit from tmux, as stated by others. To excessively add to what's already been mentioned:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |