docs/132959: description mismatches on xterm/termcap, fortune/freebsd-tips

[Kazuo Dohzono]

>Number:         132959
>Category:       docs
>Synopsis:       description mismatches on xterm/termcap, fortune/freebsd-tips
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 23 08:30:04 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Kazuo Dohzono
>Release:        7.2-PRERELEASE
>Organization:
>Environment:
FreeBSD abacus3 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0: Wed Mar 18 12:29:48 JST
2009     dohzono at abacus3:/usr/local/tmp/obj/usr/src/sys/GENERIC  i386

>Description:
/usr/share/games/fortune/freebsd-tips tells that `xterm' and
`xterm-color's are different, but /usr/share/misc/termcap tells that
they are the same entry.

freebsd-tips:
| If you are running xterm, the default TERM variable will be 'xterm'.  If you
| set this environment variable to 'xterm-color' instead, a lot of programs will
| use colors.  You can do this by
| 
| 	TERM=xterm-color; export TERM
| 
| in Bourne-derived shells, and
| 
| 	setenv TERM xterm-color
| 
| in csh-derived shells.

termcap:
| xterm|xterm-color|X11 terminal emulator:\
| 	:ti@:te@:tc=xterm-xfree86:

>How-To-Repeat:

>Fix:
There would be two solutions:

1) Make termcap's `xterm' to be monochrome (and deriver xterm-color
from it). Or, 

2) Change freebsd-tips to describe current termcap's entries (and
create another monochrome `xtermM' entry as termcap's Note says as
below).

| #	that limit.  The 'xterm' description supports color.  The monochrome
| #	'xtermm' drops color in favor of additional function keys.  If you need


>Release-Note:
>Audit-Trail:
>Unformatted: