3 ms·

I can't figure out an use case for your setup, can you help a bro out?

• Jtsummers 4y ago
  Nested sessions. Hypothetical: local computer with screen \ \ ssh/mosh to remote A, run screen \ \ ssh/mosh to remote B, run screen If each uses the same prefix (the default is C-a for screen, C-b for tmux) then you have to send it multiple times to send a command to the screen sessions on either of the remote systems. If you give each a unique prefix then you can send the prefix once and it goes directly to the desired screen session. Easier to give each system its own prefix that's constant regardless of depth, though, than trying to remember "Did I connect to A first or B first today?". Or, better in my experience, don't nest them. It's a pain however you choose to deal with the prefix problem.
• philsnow 4y ago
  Instead of keeping N terminals open for N projects, I usually keep only one open and put each project in a screen session, then wrap them all in a “meta” session. I started using this pattern before I moved to macos, but now that I’m usually on a mac, it helps because I still haven’t gotten used to macos window / desktop management. Managing one terminal is easier than a half dozen.
  • ilyt 4y ago
    I do that except with terminal emulator sessions. One window with few tabs per virtual desktop, as I rarely need to have more than 2-3 projects open at the time it works fine. But... isn't tmux sessions exactly what you'd need for that? One session per project, then just connect to servers from within tmux windows There is even switch-tree (default C-b w) that will show each session with every sub-window in it, and even preview window below that showing each terminal (refreshable via space)