Re: xterm termcape :ti_at_:te_at_:

On Mon, 25 Apr 2011 07:00:39 -0400
Thomas Dickey <dickey_at_radix.net> wrote:

> On Mon, Apr 25, 2011 at 09:52:24AM +0200, Gary Jennejohn wrote:
> > On Sun, 24 Apr 2011 20:23:14 -0400
> > Thomas Dickey <dickey_at_radix.net> wrote:
> > 
> > > On Mon, Apr 25, 2011 at 08:37:05AM +0900, Randy Bush wrote:
> > > > no help from the following:
> > > > 
> > > > *** termcap~    Fri Mar 18 14:34:01 2011
> > > > --- termcap     Sun Apr 24 23:33:52 2011
> > > > ***************
> > > > *** 3131,3136 ****
> > > > --- 3131,3137 ----
> > > >   #
> > > >   # Customization begins here.
> > > >   xterm-xfree86|xterm terminal emulator (XFree86):\
> > > > +       :te=\E[?1049l:ti=\E[?1049h:\
> > > >         :tc=xterm-new:
> > > 
> > > At this point, I'd check if less is using that entry
> > > (ktrace or truss should be able to show the open's on the termcap database,
> > > for instance).
> > > 
> > > Also, I seem to recall some discussion about less' -X (--no-init)
> > > option.  It's possible that someone's patched "less" for FreeBSD
> > > to make that -X option more or less permanent.  That would be
> > > consistent with omitting ti/te from the termcap.
> > > 
> > 
> > This may not be too helpful, but it works with rxvt and less, i.e. the
> > old screen contents are preserved and appear again after leaving less.
> 
> Well, that would address the issue with "less" (if it used the same
> behavior in either terminal).  rxvt should be setting $TERM to some
> "rxvt" name though, since its function-keys differ from xterm's.
> 

That's why I mentioned it, although I didn't compare the termcap entries
for xterm and rxvt.

> (I seem to recall that some packages for it used to set TERM to "xterm",
> under the supposition that a poor match was better than none).
> 

Mine sets it to rxvt.

I tried setting TERM to rxvt in xterm, but of course it didn't work.

-- 
Gary Jennejohn