tmux control mode + EternalTerminal: cannot re-attach to already attached (but dead) session
- iTerm2 version: 3.3.7
- OS version: 10.14
- Attach ~/Library/Preferences/com.googlecode.iterm2.plist here com.googlecode.iterm2.plist
- Attach a debug log: probably no need?
- Are you reporting a performance issue, excessive CPU usage, or a hang? no
- Are you reporting a crash? no
- Are you reporting excessive memory usage? no
- EternalTerminal version: 6.0.4, dev master e845900da043f9da99e47a73ba0c0475f343c1e2.
Detailed steps to reproduce the problem:
- Log in to remote with
et user@ip-addr
. - Create a
tmux
session withtmux -CC
, bury the original one. - Make the server change its IP address. The session will freeze.
-
et user@new-ip-addr
. -
tmux -CC a -d
.
What happened:
A message box "This instance of iTerm2 is already attached to this session" pops up. It has 2 buttons: "Reveal" and "OK". "Reveal" opens a "tmux Dashboard" list with the frozen sessions, "Attach" or "Detach" have no effect. "OK" just closes the dialog.
What should have happened:
I think we need a "detach the original session" option. This was the intent of the command. I believe tmux does offer this option, because this is what I see in a new session:
----------------------------
esc Detach cleanly.
X Force-quit tmux mode.
L Toggle logging.
C Run tmux command.
tmux a -d
without -CC
works fine. It might be a workaround, but I don't really want (or know) tmux
hotkeys.
It works with ssh
instead of et
.
Edited by Victor