8 ms·
I use screen, but there's no real reason for it but inertia. I don't know of anything it does better than tmux (except, perhaps, being available more places).
by dllthomas 10y ago
I use screen, but there's no real reason for it but inertia. I don't know of anything it does better than tmux (except, perhaps, being available more places).
I use it, plus some scripts, to keep my work separated into various contexts. See https://github.com/dlthomas/config-files/blob/master/bin/session https://github.com/dlthomas/config-files/blob/master/bin/ses... and https://github.com/dlthomas/config-files/blob/master/.bash.d/session.bashrc https://github.com/dlthomas/config-files/blob/master/.bash.d...
The single biggest win is keeping a separate bash history per context. But it's also very handy to define context specific functions and aliases, cd at start to a relevant directory, etc.
Putting it all inside screen means that I can trivially start a new shell in the same context and gives a nice grouping.
- archmonk 10y agoInteresting I didn't know that in screen you could isolate bash history per context.
- dllthomas 10y agoIt's not screen doing the work. Screen is just a process that spawns other processes, and like always those inherit environment variables. The script I have that starts screen defines a variable called "SESSION" beforehand, and that's used in my bashrc to set HISTFILE (and other things). Screen is just how I organize it.
- atmosx 10y agoWhat I've always missed going from screen to tmux is the ability to keep logs. "screen -L" will do the trick, while in tmux I need to install a plugin.