TMUX: hype or function
-
Scanning through my recent feed, I found mention of using TMUX in Linux. Has anyone been using this, is there benefit to using it?
tmux is a terminal multiplexer for Unix-based operating systems. Simply put, it acts as an add-on to an existing terminal.
-
@gjacobse said in TMUX: hype or function:
Scanning through my recent feed, I found mention of using TMUX in Linux. Has anyone been using this, is there benefit to using it?
tmux is a terminal multiplexer for Unix-based operating systems. Simply put, it acts as an add-on to an existing terminal.
Off the top of my head, tmux is like screen. It's a way to manage multiple terminal sessions.
I used to use them often, but today I ask myself why I feel it's necessary? What's failed that I need multiple terminal sessions at one time. Every time it's either "this should be a VM" or "this should be a container".
-
I used to use tmux very heavily. I recently mostly used Zellij, which is a similar tool but written in Rust.
However, now I almost exclusively use multiple buffers in neovim with a terminal overlay.
Once really nice thing about tmux is you can keep jobs running in the session after disconnecting from SSH. So if you have a long running job (like a large rsync) you can just disconnect from the session on the server but let it keep running.
-
Before using the buffers in neovim, I would have multiple windows open, usually one for each code base, and then I could have multiple panes open in each window for different files, a terminal, etc. Now I mostly just have a tab in the terminal for the codebase and then I will have buffers open for multiple files.
-
@travisdh1 said in TMUX: hype or function:
Off the top of my head, tmux is like screen. It's a way to manage multiple terminal sessions.
Yeah, it's like an upgraded screen I think. Screen is fine for me and I started on that. Useful tools, not sure if there is much "hype" around them.
-
@stacksofplates said in TMUX: hype or function:
Once really nice thing about tmux is you can keep jobs running in the session after disconnecting from SSH
Which means, for those who miss the implication, that you can reconnect to the same session from a different location.
-
@stacksofplates said in TMUX: hype or function:
Once really nice thing about tmux is you can keep jobs running in the session after disconnecting from SSH. So if you have a long running job (like a large rsync) you can just disconnect from the session on the server but let it keep running.
I often use
nohupfor this. -
@scottalanmiller said in TMUX: hype or function:
@stacksofplates said in TMUX: hype or function:
Once really nice thing about tmux is you can keep jobs running in the session after disconnecting from SSH
Which means, for those who miss the implication, that you can reconnect to the same session from a different location.
Yeah. You can even share the socket so that multiple people can view a single session. Good for pairing with others.
Which is how things like tmate operate
