X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-Id:	<5.1.0.14.2.20020318212656.02faa510@pop.escape.com>
X-Sender:	pjfarley3 AT pop DOT escape DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 5.1
Date:	Mon, 18 Mar 2002 22:04:39 -0500
To:	djgpp-workers AT delorie DOT com
From:	"Peter J. Farley III" <pjfarley3 AT escape DOT com>
Subject:	Re: Need help with @xref for dir.txi
Cc:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
In-Reply-To:	<Pine.SUN.3.91.1020318081554.4450J-100000@is>
References:	<5832-Mon18Mar2002062936+0200-eliz AT is DOT elta DOT co DOT il>
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

At 08:22 AM 3/18/02 +0200, Eli Zaretskii wrote:
<Snipped>
 >I have an idea what could go wrong: did you test this with a normal
 >Info file, or just with DIR?

Just with DIR.

 >I did the former (my DIR files are too precious to futz with 
;-).  That
 >is, I produced a something.info file from dir.txi, and then told Info 

 >to display that file.
 >
 >If the same works for you, it's possible that the special treatment
 >Info gives to DIR files somehow gets in the way.
 >
 >To make sure your new makeinfo indeed produces the correct 
information
 >for the anchors, look at the tag table at the end of the Info files 
it
 >generates.  There's a "Ref:" line there for each anchor; the number
 >after "Ref:" is the byte offset, counted from the first Node line of
 >the file, of the position where you should land when you follow the
 >cross-reference to that anchor.  You should see that the old makeinfo 

 >produces identical offsets for all the anchors in a menu, whereas the 

 >patched makeinfo produces a different number for each anchor.

OK, I rebuilt my dir-with-xref fragment in the /info directory with the 
patched 4.1 makeinfo, and proved that my first test was accessing an 
older copy of DIR built without the 4.1 patch.  Both the 4.1 ginfo and 
the stock 2.03 info can correctly access the @xref nodes built with the 
patched 4.1 makeinfo.

Sorry for the false bug report.  Your patch appears to work as 
advertised.  The old makeinfo built "Ref:" lines all with the same byte 
value (744 in my case).  The patched 4.1 makeinfo generates "Ref:" 
lines with increasing values, and info (both versions) puts the cursor 
at the @xref points I specified, as required.
---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org)

- Raw text -