| 1 |
On Tue, 28 Jan 2014 01:20:59 +0000 (UTC), Martin Vaeth wrote: |
| 2 |
|
| 3 |
> I suggest that you try tmux (or screen) - this is far superiour to |
| 4 |
> multitab since you can easily also put it to the background or |
| 5 |
> access it remotely |
| 6 |
|
| 7 |
Screen and tabs are different solutions to different problems. When |
| 8 |
working with multiple SSH sessions to different machines, and not using |
| 9 |
ClusterSSH, I find it most convenient to have a tab for each host, with |
| 10 |
a screen session in that tab. |
| 11 |
|
| 12 |
> My default zsh login files start a tmux session automatically |
| 13 |
|
| 14 |
I found this incredibly messy when running one screen session on the local |
| 15 |
machine, with each terminal connected to a different host, which in turn |
| 16 |
ran screen (like you, my profile loads or starts a screen session for SSH |
| 17 |
logins). The main issue with nested screens being that the command |
| 18 |
keystrokes seemed to always go to the wrong instance of screen. |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
Neil Bothwick |
| 23 |
|
| 24 |
Not one shred of evidence supports the notion that life is serious. |
Archives