4 ms·
I agree with you. I suspect it is around understanding that tmux is a server, which you start and connect to. Its my daily driver, but that means when I am in
by roomey 4y ago
I agree with you. I suspect it is around understanding that tmux is a server, which you start and connect to.
Its my daily driver, but that means when I am in bare zsh, without tmux, it usually doesn't "work" for me. So, I can understand if someone is just spinning up tmux occasionally (to keep some long running program from stopping) that it can be a bit jarring. In some senses, the simpler 'screen' might actually be a better fit for that.
But yea, using tmux every day for years you become very thankful of how it operates, keeps variables isolated, you tend to work in one session per project (and it's great for not mixing them up).
But yea, it wouldn't be great if you are working away on something, then half way through just "start a session".
Tmux isn't going to do what the op is trying to do I suspect.
I'm a big tmux fan, it is awesome (in case that wasn't clear)
- ghshephard 4y agoInteresting that you do one session per project - I've experimented occasionally with that, but I ended up in the one window per project, and then break up the work in to 4-8 panes (more or less). Every window gets a name (my new window shortcut requires it) so it's relatively straightforward (for me) to find the project context, particularly as the bash_history is named after the window, and shared between panes (so you can pull the entire work history for a project based on its name).