[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] ignoring Info extensions

From: Juri Linkov
Subject: Re: [PATCH] ignoring Info extensions
Date: Fri, 02 Apr 2004 06:27:11 +0300
User-agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux)

"Eli Zaretskii" <address@hidden> writes:
>> From: Juri Linkov <address@hidden>
>> Date: Thu, 01 Apr 2004 19:33:15 +0300
>> There are many other Info manuals that have a string `*Note:'
>> which is treated incorrectly by Info readers.
> What manuals are those?

I just ran on Debian GNU/Linux (the biggest Info base I was able to find):

find /usr/share/info -type f -exec zgrep -iH "\*Note[^ \t]" {} \;

and it reported 116 matches: 6 in cvs, 22 in gawk, 11 in gcc, 16 in gtk,
20 in libc, and many other files.  And _none_ of them is an Info reference.

>> What do you think
>> about interpreting a `*Note' as an Info reference only if it
>> has whitespace around it, i.e. if it matches the following regexp?
>> [ \t\n]+\*[Nn]ote[ \t\n]+
> I don't think it is wise for us to make changes in the de-facto format
> of Info files.  The current format clearly doesn't require any
> whitespace, so you are suggesting an incompatible change.

I am not aware of any Info files with references without whitespace
after `*Note'.  Perhaps somewhere such files may exist that was
generated by a program other than makeinfo, or was hand-written?

OTOH, while the change in Info readers will make such possible
references unavailable for navigation, it will fix the problem
in known Info files.  For example, look at the node
(info "(gtk)GtkNotebook") in the latest GTK version.
With Info-hide-note-references=t it is so distorted that
it is almost unreadable.

Juri Linkov

reply via email to

[Prev in Thread] Current Thread [Next in Thread]