From: Conor Daly (conor.daly at domain met.ie)
Date: Wed 16 May 2001 - 15:43:36 IST
On Wed, May 16, 2001 at 03:22:10PM +0100 or thereabouts, Colm Buckley wrote:
> On Wednesday 16 May 2001 15:14, Conor Daly wrote:
> > A gnome term returns "xterm" in $TERM but that doesn't necessarily
> > indicate what termcap entry it's using.
> Actually, it does. Curses uses the TERM variable to *determine* which
> termcap/terminfo entry to use. It's not the gnome-terminal which
> reads termcap/terminfo, it's curses-using progrms (like vim).
> However, it does appear from a little googling that gnome-terminal
> doesn't accept the titeInhibit resource, so this might be a blind
> However, a lot of poking in the vim help files reveals that putting:
> :set t_ti= t_te=
> in your .vimrc will inhibit the sending of these codes, so that might
> work for you. Note : other curses programs like less and whatnot
> will still exhibit the old behaviour - if you want this to apply to
> all programs, you could edit the terminfo source and change the smcup
> and rmcup entries for xterm... (see "man tic" and "man terminfo").
OK, I've given him
in his .Xdefaults and
:set t_ti= t_te=
in his .exrc So he gets the following..
In an xterm, no alternate screen is used.
In a gnome-term, when vi exits, its stuff is left on screen, when man
(that's less anyhow innit?) exits, the screen clears.
I think that's enough to keep him happy since he can do all that as a user.
-- Conor Daly Met Eireann, Glasnevin Hill, Dublin 9, Ireland Ph +353 1 8064217 Fax +353 1 8064275 ------------------------------------ 2:36pm up 2 days, 15:40, 4 users, load average: 1.00, 1.00, 1.00
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:10:19 GMT