Hi,
...on Sun, Apr 10, 2011 at 12:59:43PM +0200, Karl Ferdinand Ebert wrote:
> On Thursday 07 of April 2011 23:14:20 Alexander Bochmann wrote:
> > The workaround I described in the original report (commenting out
> > the two statements "setenv COLUMNS" and "setenv LINES" from
> > both /etc/cs
On Thursday 07 of April 2011 23:14:20 Alexander Bochmann wrote:
> Hi,
>
> ...on Thu, Apr 07, 2011 at 12:41:49PM +0200, Karl Ferdinand Ebert wrote:
> > Could you provide us with additional information about your shell
> > configuration as requested by the last email from Romain?
>
> Sorry, I see
Hi,
...on Thu, Apr 07, 2011 at 12:41:49PM +0200, Karl Ferdinand Ebert wrote:
> Could you provide us with additional information about your shell
> configuration as requested by the last email from Romain?
Sorry, I seem to have missed that mail. Thanks for the extensive
reply.
I agree that th
Hello Alexander,
Could you provide us with additional information about your shell
configuration as requested by the last email from Romain?
Best regards,
Ferdinand
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
Hi,
the problem still exists in 1.3-2.
Correction to the initial description: With mutt, it manifests
itself right away without resizing the terminal, as the status line
makes the terminal shorter by one line. Resizing actually
helps for the active window, as LINES and COLUMNS get overwritten
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 r
7 matches
Mail list logo
