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

Previous Next

Full log

View this message in rfc822 format

From: Protesilaos Stavrou <info <at> protesilaos.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 52126 <at> debbugs.gnu.org, larsi <at> gnus.org, Stefan Kangas <stefan <at> marxist.se>, kyle <at> kyleam.com, rgm <at> gnu.org
Subject: bug#52126: Problematic characters in info node names
Date: Mon, 29 Nov 2021 20:04:37 +0200

On 2021-11-29, 19:52 +0200, Eli Zaretskii <eliz <at> gnu.org> wrote:

>> From: Stefan Kangas <stefan <at> marxist.se>
>> Date: Mon, 29 Nov 2021 09:44:17 -0800
>> Cc: 52126 <at> debbugs.gnu.org, Protesilaos Stavrou <info <at> protesilaos.com>,
>>  Kyle Meyer <kyle <at> kyleam.com>, Glenn Morris <rgm <at> gnu.org>
>> 
>> 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.

Thanks!

I just removed the problematic characters from my repo.  Though this
change will be brought into emacs.git as part of my next tagged release
(in a few weeks).

Two questions then:

1. Do you want me to change this now on the trunk?
2. This affects the emacs-28 branch.  Should I patch that as well?

-- 
Protesilaos Stavrou
https://protesilaos.com

Previous Next

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