Hi, Sorry for taking so long to get to this bug...
I discussed this with tmux's upstream author, and our conclusion is that while tmux could certainly support blacklisting some environment variables as you suggest, the real problem seems to be in your shell, namely ... > A user with csh or tcsh as login shell starts tmux and resizes the > terminal. All new tmux windows will have the original COLUMNS and > LINES values from before resizing the terminal in their > environment. ... this seems to suggest that tcsh doesn't set the values of LINES and COLUMNS at startup based on the current terminal, but uses old values if they're present. This is not what bash, zsh and ksh (and probably others) do, they always update the values themselves to match the terminal settings. > [...] Resizing actually helps for the active window, as LINES and > COLUMNS get overwritten with the correct new window size. ... and this suggests that tcsh correctly handles SIGWINCH when it receives it. So my suggestion is to investigate why, in your configuration, the values of LINES and COLUMNS are not explicitly set when the shell starts. Alternatively, you could arrange for SIGWINCH to be sent to your shell from your init files. And fwiw, my zsh configuration exports COLUMNS, it's present in the global environment, yet zsh/zle automatically updates it to the correct values when it starts. Thanks, -- Romain Francoise <rfranco...@debian.org> http://people.debian.org/~rfrancoise/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
