Both terminal multiplexers (screen, tmux) and keyboard-driven tiling window managers (ratpoison, dwm, xmonad) provide similar functionality. Is there any benefit in using both at the same time? What about problems that may arise?
Tell me more
×
Unix & Linux Stack Exchange is a question and answer site for
users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.
|
|
|||||||||||
|
|
I use dwm and tmux. Before learning to use tmux, I would have multiple terminals open for different things, and have them in different tags. Now I can run everything inside of one tmux session, under a single tag, and can detach and reattach without losing state if I need to restart X. |
|||
|
|
|
The added benefit of terminal multiplexers is that your multiplexer sessions will still be alive and you can reconnect to them even if X (your desktop session) crashes, or you logged out of X. |
|||
|
|
|
No. In those rare cases where screen inside of screen or tmux inside of tmux is useful, both programs provide a simple means of passing control to the nested instance. Screen offers serial console capabilities, but I just use a dedicated app (miniterm.py distributed with python) when I need that. Otherwise I can't think of anything offhand that either can do and the other can't, but one might do it simpler than the other. I would learn one or the other, and if you're curious or dissatisfied with what you picked, try the other. I prefer tmux, personally. |
|||
|
|
