Subject: Re: bin/7198: recent xterm termcap entry flakes out screen
To: ITOH Yasufumi <>
From: Mason Loring Bliss <>
List: netbsd-bugs
Date: 03/19/1999 08:15:07
On Fri, Mar 19, 1999 at 09:08:26PM +0900, ITOH Yasufumi wrote:

> It seems the TERMCAP environment variable set by screen
> exceeds 1023 bytes long.
> (Bug of screen?)

Hm. It's 1007 bytes long when I've got the older termcap.db in place.

> > Use an older termcap. Diffs that apply to 1999.03.17's termcap are included,
> > below.
> Does this really fix?

Yes. The problem definitely isn't there when I swap in the older termcap, but
leave the vi, screen, and xterm versions the same. The problem definitely is
there with the newer termcap, and everything else the same.

> Screen sets its own termcap entry in TERMCAP variable,
> and I think reverting the /usr/share/misc/termcap{,db} doesn't help.

Doesn't it pull this from /usr/share/misc/termcap{,db}?

> I think the following will be a work-around of the problems
> Type
> 	% unsetenv TERMCAP	# if you are using csh
> or
> 	% eval `tset -I -s`
> in a window of screen
> and then,
> 	% vi

Hm. I think it would be better if whatever it is in the termcap ended up
not overflowing whatever it is that it's overflowing. I don't like the
idea of having to manually toast the TERMCAP environment variable. It
gets trickier when something that's not a shell calls vi. Somehow fixing
the termcap is a cleaner solution.

Mason Loring Bliss             ((  "In the drowsy dark cave of the mind dreams  ))  build  their nest  with fragments  dropped ((   from day's caravan." - Rabindranath Tagore