Package: tmux
Version: 1.3-1
Severity: normal

When tmux is used with csh/tcsh on Debian, the initial values of 
the COLUMNS and LINES environment variables leak into tmux' global 
environment, and therefore into the environment of each new window 
in the session.
Every terminal application that relies on these variables (mutt 
being an example) will have a garbled display when being started 
after the terminal has been resized from it's original size.

The bug was previously filed as 602674, before I understood why the 
problem occurs.

Reproduction:

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. 
The original values show up when running "tmux show-environment -g".

Workaround:

Both /etc/csh.cshrc and /etc/csh.login on Debian contain the following 
two statements:

       setenv COLUMNS
       setenv LINES

When these lines are removed, the COLUMNS and LINES variables disappear 
from tmux' global environment and everything works as expected.

While it's possible to change the shell rc and login files, I think 
something in the line of blacklisting these variables from tmux's 
global environment would be a more thorough solution.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32.23-grsec (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages tmux depends on:
ii  libc6                    2.11.2-7        Embedded GNU C Library: Shared lib
ii  libevent-1.4-2           1.4.13-stable-1 An asynchronous event notification
ii  libncurses5              5.7+20100313-4  shared libraries for terminal hand

tmux recommends no packages.

tmux suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to