On Sun, May 05, 2002 at 03:31:47PM -0400, Andy Sparrow wrote: > Both of which are specifically stated to be incorrect (with an explanation > why) by the maintainer of XFree86 xterm on his web page. > > XFree86's 'xterm' is a color xterm, and has been for years. We don't ship > their termcap entry. > > Substituting the XFree86 termcap/terminfo entries for ours apparently fixes > the currently broken behaviour.
Yes, but other people does not like some "features" of the xterm termcap entry supplied by XFree86. > > Other OSen do not have xterm-color, though (as has already been > > mentioned, Solaris), so this breaks as soon as you ssh to one of these > > remote machines. As someone who runs Solaris servers from a FreeBSD > > desktop I do this a lot. > > What he said :) > > Also, some OS's have an entry for 'xterm-color' that is NOT the XFree86 xterm, > but an obsolete xterm variant, and this will also break. And I absolutely agree. In fact we also have Solaris and Irix machines, which I hacked (adding a xterm-color entry, or redefining TERM in the session startup scripts). What I wanted to say is that defining termName in XTerm-color is *coherent* with FreeBSD having two distinct termcap xterm entries: mono and color. However, I also think that having those two entries is *bad*. IMHO, the xterm and xterm-color entries should be merged in only one xterm supporting color. Cheers, JMA -- ****** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
