Re: titeInhibit ignored by gnome-terminal ?

[mcompengr earthlink net]

Jeff,

There's nothing worse than problem terminal settings.  I shy away
from X resourse solutions (in general too) because the final value
accepted is in the executable, and can not be overidden, if set there.

My approach is in the stty/tset and /etc/termcap area.  The latter
is the easiest for me.  In an emergency I setenv TERM to a non-existant
value which hopefuly causes a fallback to some default.  If you look
in /etc/termcap you should see strings beginning in column one that
are followed by a |.  These are the available values for the TERM
env.  Following the name is a bunch of parameter/setting pairs.  The
parameter name begins with a :.  Now, the :te parameter is the one
we DON'T want, in order to inhibit that flipping.

You can have your gnome-terminal invoked with the --login flag, and
then put setenv TERM <foobar> in your .login file.  Or, type setenv
TERM <foobar> as the first command.  This is for csh/bash/tcsh etc.
Korn syntax differs (no setenv).

---David



> I have XTerm.VT100.titeInhibit:  true
> 
> in my .Xdefaults. Nonetheless, while xterm pays attention to this,
> gnome-terminal doesn't. (I'm using gnome-terminal 1.1.5.)
> 
> (Background FYI: titeInhibit controls whether apps such as less, more,
> vi, mutt, and so forth that ask to use the xterm's alternate screen
> actually flip to that screen or not. More practically, this means it
> controls whether quitting vi, less, etc. leaves you looking at what
> you were looking at a moment ago or what you were looking at before
> you started that app.
>
> Tia for any pointers.
> 
> -- 
>  Jeff Abrahamson
>  610/270-4845
>  abrahj01 molbio sbphrd com
> 
>  (home email is jeff_abrahamson purple com)
>