On Sat, Jul 23, 2005 at 10:44:49AM -0400, Thomas E. Dickey wrote:
> >I'm a bit confused really; the xterm-r6 definition in misc/terminfo.src
> >has kdch1=\E[3~.  The xterm-r6 definition in debian/xterm.ti has
> >kdch1=\177, and I'm pretty sure we get that from the xterm source
> >distribution... I wonder why they diverged?
> 
> I'm not 100% sure, since some of the changes are old.  I see looking at 
> xterm's terminfo history that kdch1 was originally \E[3~. In August 1996, 
> there's a change to make it \177.  I don't see that in any of my patches 
> (though I did make other changes to the terminfo around then - added the 
> ech string).
> 
> The XFree86 CVS only shows "updates" for the change comment on that file. 
> So who and why the change was made - I doubt that the answer is 
> forthcoming.  I don't see any xterm-fixes for that period in XFree86's
> changelog other than mine, and doubt that David Dawes recalls who 
> submitted the change.
> 
> ncurses's terminfo is maintained separately, and I probably ignored this 
> since when I compare the two, I'm focused on the XFree86 flavor - 
> xterm-r6 and xterm-r5 are in xterm's file just for convenience.

Right, I understand.

Since the terminfo shipped with xterm is primarily of interest for the
"real" and current xterm, and the terminfo shipped with ncurses is
supposed to cover a wide variety of all kinds of oddball terminals, I
am inclined to take only the entries describing our xterm from
debian/xterm.ti (i.e. from the xterm source); let ncurses's
misc/terminfo.src supply things like xterm-r6.  As a side effect, that
would fix this problem for Vincent.  Does that sound reasonable?

Hmm, I just checked - Red Hat's xterm-r6 terminfo uses \177 so they
must be getting it from xterm.  My Solaris box is down.  HPUX uses
kbs=\177 but has no kdch1 at all (that's for "xterm").  Darwin uses
kdch1=\E[3~ for xterm and xterm-r6.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to