unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Glenn Morris <rgm@gnu.org>,  Stefan Kangas <stefan@marxist.se>
Cc: 52126@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
	Protesilaos Stavrou <info@protesilaos.com>
Subject: bug#52126: Problematic characters in info node names
Date: Mon, 29 Nov 2021 23:31:30 -0500	[thread overview]
Message-ID: <87tufue02l.fsf@kyleam.com> (raw)
In-Reply-To: <60pmqihlmr.fsf@fencepost.gnu.org>

Glenn Morris writes:

> Stefan Kangas wrote:
>
>> Did something change here since the above note in admin/release-process
>> was written in 2013 (commit 16bcc96df4)?
>
> Yes. It's easy to find old versions of the Texinfo manual, eg
> http://www.nongnu.org/texi2latex/texinfo/Node-Line-Requirements.html
>
> Newer Texinfo is less strict, but Emacs configure still claims to
> support 4.13.

I wonder whether 4.13 actually has a problem with the cases flagged in
this issue, where the parentheses are not at the start of the text.
Texinfo's ab404029d0 (parens only disallowed when looks like an external
manual ref, 2011-09-18) made the following text change:

   @cindex Characters, invalid in node name
   @cindex Invalid characters in node names
   @cindex Node names, invalid characters in
  -Unfortunately, you cannot use periods, commas, colons or parentheses
  -within a node name; these confuse the Texinfo processors.  Perhaps
  -this limitation will be removed some day, too.
  +Unfortunately, you cannot use periods, commas, or colons within a node
  +name; these confuse the Texinfo processors.  Also, a node name may not
  +start with a left parenthesis and contain a right parenthesis, as in
  +@code{(not)allowed}; this specifies an external manual in Info.
  +Perhaps these limitations will be removed some day, too.

That looks to be a pure documentation update to more accurately describe
the restrictions.  The commit message links to a thread [*] that seems
to confirm that.  There Patrice Dumas says

  What is not allowed, in reality, and leads to an error message is parentheses
  beginning at the beginning of the node name as you said:
  
   @node (man)bad
  
   c.texi:6: Syntax for an external node used for `(man)bad'

[*] https://lists.gnu.org/archive/html/bug-texinfo/2011-09/msg00024.html





  reply	other threads:[~2021-11-30  4:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 15:24 bug#52126: Problematic characters in info node names Stefan Kangas
2021-11-26 16:26 ` Eli Zaretskii
2021-11-29 16:03 ` Lars Ingebrigtsen
2021-11-29 17:44   ` Stefan Kangas
2021-11-29 17:52     ` Eli Zaretskii
2021-11-29 18:04       ` Protesilaos Stavrou
2021-11-29 18:07         ` Eli Zaretskii
2021-11-29 19:32           ` Protesilaos Stavrou
2021-11-29 19:46             ` Eli Zaretskii
2021-11-29 20:07               ` Protesilaos Stavrou
2021-11-29 20:32                 ` Eli Zaretskii
2021-11-29 20:56                   ` Protesilaos Stavrou
2021-11-30  3:25                     ` Eli Zaretskii
2021-11-30  6:39                       ` Stefan Kangas
2021-11-30  7:16                         ` Protesilaos Stavrou
2021-11-30  7:41                           ` Stefan Kangas
2021-11-30 16:48                           ` Eli Zaretskii
2021-11-29 18:31       ` Stefan Kangas
2021-11-29 18:17     ` Glenn Morris
2021-11-30  4:31       ` Kyle Meyer [this message]
2021-11-30  4:39   ` Kyle Meyer
2021-12-03  1:12     ` Stefan Kangas
2021-12-03  1:45       ` Kyle Meyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tufue02l.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=52126@debbugs.gnu.org \
    --cc=info@protesilaos.com \
    --cc=larsi@gnus.org \
    --cc=rgm@gnu.org \
    --cc=stefan@marxist.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).