On Fri, Sep 28, 2007 at 11:32:38AM +1200, Atom Smasher wrote:
> > > cool... and that will include the shell's opinion of
> > > MRXVT_TABTITLE?
> >
> > Thats not possible. It can only include the current tab title. Wether or
> > not your shell updates MRXVT_TABTITLE to make it point to the current
> > tab title is up to your shell :)
> ================
>
> if i set the shell variable FOO=bar, then it will (in the near future?) be
> possible to export that to the bell-command? but that won't be possible
> with MRXVT_TABTITLE?
>
> without going through the source code, i'm not sure why that's not
> possible. can you give a brief explanation? or am i not understanding
> this?
1. Mrxvt can happily do FOO=bar *BEFORE* starting the shell. In this
case the shell will see it. The shell will then inherit a *copy*
of the environment when starting.
2. Nothing mrxvt does after the shell starts can alter the shells
copy of the environment.
3. Nothing the shell does ever can alter mrxvt environment.
Thus there is nothing mrxvt can do that will keep the shell's copy of
MRXVT_TABTITLE in sync with the current tab title. However we can set it
correctly for all processes we fork in future (e.g. bellCommand).
GI
--
'Civilization' -- Going from shoeless toes to toeless shoes.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Materm-usage mailing list
Materm-usage@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/materm-usage
Mrxvt home page: http://materm.sourceforge.net
