Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: updating the shell environment in screen (was Re: prompt and ssh)
- X-seq: zsh-users 14179
- From: Vincent Lefevre <vincent@xxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: updating the shell environment in screen (was Re: prompt and ssh)
- Date: Wed, 27 May 2009 03:10:35 +0200
- In-reply-to: <20090526145145.GA28557@xxxxxxxxx>
- Mail-followup-to: zsh-users@xxxxxxxxxx
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <e7db6e960905190954j7be72739p6b521bca8e90fe7f@xxxxxxxxxxxxxx> <20090519200217.35368.qmail@xxxxxxxxxxx> <20090521074103.GN27141@xxxxxxxxxxxxxxxxxxx> <20090524222632.GC26513@xxxxxxxxx> <154941E5-F5C5-4B9E-97E1-17EFABF9CDC8@xxxxxxxxxxx> <20090526145145.GA28557@xxxxxxxxx>
On 2009-05-26 07:51:46 -0700, Wayne Davison wrote:
> I forgot to mention that I have term-conditionional setup of my preexec
> function. Inside screen, my $TERM is always "screen". There could be a
> problem if I login to a remote system from inside screen and that remote
> system had this rc code, though, since the TERM=screen code would
> trigger when it shouldn't. Another possible triggering variable is
> $WINDOW, which will be set to the screen's window number when inside
> screen -- as long as ssh is not set to pass-through this variable, it
> may well be a better trigger mechanism.
You may need to use both, since if you start a terminal (e.g. xterm)
from screen, the WINDOW variable will be inherited.
--
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
Messages sorted by:
Reverse Date,
Date,
Thread,
Author