On Tue, Jun 21, 2005 at 01:34:22AM -0500, Branden Robinson wrote:
> > I know the terminfo was upgraded, and I wouldn't be surprised by a
> > version dependence on xterm, but I thought it was around #192.
> 
> We ship XTerm #200 in xterm 4.3.0.dfsg.1-14:

Yes, I know - that's why I assume the dependency is not the problem.

> > The terminfo we're shipping is the same as the one in
> > /usr/share/doc/xterm/xterm.terminfo.gz in 4.3.0.dfsg.1-14.  And that's in
> > sarge.
> 
> I'm sorry, but I must differ with you there:
> 
> 589 {0} [EMAIL PROTECTED]:~# zcat /usr/share/doc/xterm/xterm.terminfo.gz | 
> md5sum
> 149359a0e57bff4d33bc74549812286f  -
> 590 {0} [EMAIL PROTECTED]:~# cat /etc/terminfo/x/xterm | md5sum
> a27bce1c0ad7de297b3fd0fad07ee3b6  -

The former is a source file, the latter is a compiled file (via tic).

> Uh, now I'm starting to get confused:
> 
> 603 {0} [EMAIL PROTECTED]:~# infocmp -F /etc/terminfo/x/xterm 
> /tmp/xterm.terminfo-from-XTerm-200
> "/etc/terminfo/x/xterm", line 1, col 1: Illegal character (expected 
> alphanumeric or @%&*!#) - '^Z'

You will need to run tic on the one from /usr/share/doc to compare it;
be sure to run TERMINFO=/tmp/path tic, so that it does not overwrite a
system file.

> 604 {0} [EMAIL PROTECTED]:~# file /etc/terminfo/x/xterm
> /etc/terminfo/x/xterm: RISC OS archive (spark format)

It's got no file magic.

[EMAIL PROTECTED]:~% mkdir t
[EMAIL PROTECTED]:~% cd t
[EMAIL PROTECTED]:~/t% zcat /usr/share/doc/xterm/xterm.terminfo.gz > xt.ti
[EMAIL PROTECTED]:~/t% TERMINFO=`pwd` tic xt.ti
[EMAIL PROTECTED]:~/t% infocmp -B `pwd` xterm xterm
comparing xterm to xterm.
    comparing booleans.
    comparing numbers.
    comparing strings.
        meml: '\El', NULL.
        memu: '\Em', NULL.

I'm not sure what that particular difference is, but I assume it's not
relevant.

[BTW: Reply-To the bug report is not so helpful if you'd like to see
any answer :-)]

-- 
Daniel Jacobowitz
CodeSourcery, LLC


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

Reply via email to