>Number:         1854
>Category:       bin
>Synopsis:       There are many terminal descriptions with bad (?) tc= entries
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Dec 23 01:20:00 1995
>Last-Modified:
>Originator:     Chris G. Demetriou
>Organization:
Kernel Hackers 'r' Us
>Release:        NetBSD-current as of 12/23/95
>Environment:
System: NetBSD sun-lamp.pc.cs.cmu.edu 1.1A NetBSD 1.1A (SUN_LAMP) #14: Tue Dec 19 17:58:16 EST 1995 cgd@sun-lamp.pc.cs.cmu.edu:/usr/src/sys/arch/i386/compile/SUN_LAMP i386


>Description:
	Instead of using "tc" termcap continuation entries, many
	termcap entries use "\tc".  For example:

	sun-24|Sun 24-line window:\
	        :co#80:li#24:\tc=sun:

	Our termcap code doesn't seem to handle "\tc" (and i don't know
	how, or if, it should be handled, if it's different than "tc").
	For instance, if you set your TERM environment variable to
	"sun-24" then try to run vi, you get:

	9 [sun-lamp] termcap % setenv TERM sun-24
	10 [sun-lamp] termcap % vi /etc/ttys
	Error: initscr failed: No such file or directory.
	sun-24: terminal type lacks necessary features.

	Fixing the sun-24 "\tc" to justbe "tc", then remaking the termcap
	database with cap_mkdb fixes the problem.

>How-To-Repeat:
	On a machine with an up-to-date /usr/share/misc/termcap
	and /usr/share/misc/termcap.db:

	setenv TERM sun-24
	vi /etc/ttys

>Fix:
	Find out if the "\tc" entries are right.  If so, update
	our termcap code to handle them.  If not, get the termcap
	maintainer to remove all of them from the termcap file,
	presumably replacing with them normal "tc" entries.
>Audit-Trail:
>Unformatted: