There’s a pretty good python module for talking to tmux sessions/windows/panes, etc. You can also use tmux to lay out terminals in a grid, or one big pane and some smaller ones, or some mid sized ones or whatever.
If you’re good with screen and happy with it you’d might as well stay with screen if only to not get key chords mixed up. I’d recommend tmux over screen to newbies. There are some decent screenshots of complicated tmux layouts on the internet. Depending on what i was doing I could see having a pane for giving input to a process, a pane for tail -f output or logging, etc., and a pane for btop to monitor resources.
Screen supports subdividing panes as well, though now I’m curious if tmux has better performance with panes. One issue I did have with screen was exactly that, having about 4-5 panes at once watching a process from different angles and I could tell it wasn’t running at full speed until I split up the panes. That alone could be a reason to relearn some muscle memory.
One thing I’m using has six tmux panes in a window, then another window that I forgot was running with two more panes, and that’s just for that session. I haven’t noticed any performance issues, but that could be workflow dependent.
That alone could be a reason to relearn some muscle memory.
In the before times when I was learning UNIX (ssh over dialup) screen was the confusing godsend that made it so my programs would stay running, but once I got reliable connections/workflows/some money to buy better stuff) I never really had a desire to go back and look at screen. Once I found tmux I really doubt I’ll ever revisit screen. Ctrl+b," gives you a new pane “below” and Ctrl+b, % gives you a new pane to the right. Ctrl+b,w gives you a little menu for all the sessions/windows/panes you have in tmux. set -g mouse on in .tmux.conf to click the panes. Copy/pasting text isn’t as easy as I’d like, but that’s probably a skill/configuration issue on my part. Hope that helps.
There’s a pretty good python module for talking to tmux sessions/windows/panes, etc. You can also use tmux to lay out terminals in a grid, or one big pane and some smaller ones, or some mid sized ones or whatever.
If you’re good with screen and happy with it you’d might as well stay with screen if only to not get key chords mixed up. I’d recommend tmux over screen to newbies. There are some decent screenshots of complicated tmux layouts on the internet. Depending on what i was doing I could see having a pane for giving input to a process, a pane for tail -f output or logging, etc., and a pane for btop to monitor resources.
Screen supports subdividing panes as well, though now I’m curious if tmux has better performance with panes. One issue I did have with screen was exactly that, having about 4-5 panes at once watching a process from different angles and I could tell it wasn’t running at full speed until I split up the panes. That alone could be a reason to relearn some muscle memory.
One thing I’m using has six tmux panes in a window, then another window that I forgot was running with two more panes, and that’s just for that session. I haven’t noticed any performance issues, but that could be workflow dependent.
In the before times when I was learning UNIX (ssh over dialup) screen was the confusing godsend that made it so my programs would stay running, but once I got reliable connections/workflows/some money to buy better stuff) I never really had a desire to go back and look at screen. Once I found tmux I really doubt I’ll ever revisit screen. Ctrl+b," gives you a new pane “below” and Ctrl+b, % gives you a new pane to the right. Ctrl+b,w gives you a little menu for all the sessions/windows/panes you have in tmux.
set -g mouse onin .tmux.conf to click the panes. Copy/pasting text isn’t as easy as I’d like, but that’s probably a skill/configuration issue on my part. Hope that helps.