GNU bug report logs - #52126
Problematic characters in info node names

Previous Next

Package: emacs;

Reported by: Stefan Kangas <stefan <at> marxist.se>

Date: Fri, 26 Nov 2021 15:25:02 UTC

Severity: normal

Done: Stefan Kangas <stefan <at> marxist.se>

Bug is archived. No further changes may be made.

Full log


Message #29 received at 52126 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 52126 <at> debbugs.gnu.org, larsi <at> gnus.org, info <at> protesilaos.com, rgm <at> gnu.org,
 kyle <at> kyleam.com
Subject: Re: bug#52126: Problematic characters in info node names
Date: Mon, 29 Nov 2021 10:31:50 -0800
Eli Zaretskii <eliz <at> gnu.org> writes:

>> I read in (info "(texinfo) Node Line Requirements") that:
>>
>>    * Unfortunately, you cannot reliably use periods, commas, or colons
>>      within a node name; these can confuse the Info reader.  Also, a
>>      node name may not start with a left parenthesis preceding a right
>>      parenthesis, as in '(not)allowed', since this syntax is used to
>>      specify an external manual.  (Perhaps these limitations will be
>>      removed some day.)
>
> This is mainly because of the stand-alone Info reader.  The Emacs Info
> mode copes with these characters in node names much better.
>
> So yes, it is desirable to avoid them, but it isn't a catastrophe if
> they are there.

I guess what I'm asking myself if its useful to keep this advice in
admin/release-process.

Personally, I have no strong opinion either way, but I note that
makeinfo seems to now claim to warn about any problematic cases.




This bug report was last modified 3 years and 227 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.