3.3.11 still tries to remember the window size after detached from `tmux -CC`
Thanks for filing an issue! Please answer the questions below so I can help you.
- iTerm2 version: 3.3.11
- OS version: 10.15.5 (19F101)
- Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window)com.googlecode.iterm2.plist
- Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog debuglog.txt.gz
- Attach a screen capture video if it would make the reproduction steps clearer.
- Are you reporting a performance issue, excessive CPU usage, or a hang? Please attach a sample. Instructions at https://gitlab.com/gnachman/iterm2/wikis/HowToSample
- Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logs
- Are you reporting excessive memory usage? Please attach a heap analysis: https://gitlab.com/gnachman/iterm2/wikis/heapshot
PLEASE ATTACH YOUR PLIST FILE FOR BUG REPORTS! Seriously! I'll probably ask you for it if you don’t.
Detailed steps to reproduce the problem:
- Use
tmux -CC ...
to start an tmux session - Use
tmux ...
(the same command as in step 1, just without-CC
part) to start another tmux client to the same session - Make sure the window in Step 2 is larger than the window in Step 1.
- tmux will auto accompany the smaller window, so in the client created in Step 2 it will only fill the excessive part with dots
- Now detach the client created in Step 1
What happened: tmux still remembers the client window size created in Step 1 and the window in Step 2 are still filled with dots for the "excessive part".
What should have happened: On earlier versions, as long as the smaller window is detached tmux will forget that window size, and expand the window in other clients to the next smallest window (in this case since there's only one client left, so it would be expand to full).
Edited by Yuxuan “fishy” Wang