From: Kyle Meyer <kyle@kyleam.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52126@debbugs.gnu.org, Protesilaos Stavrou <info@protesilaos.com>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#52126: Problematic characters in info node names
Date: Mon, 29 Nov 2021 23:39:55 -0500 [thread overview]
Message-ID: <87sfvedzok.fsf@kyleam.com> (raw)
In-Reply-To: <871r2zueyw.fsf@gnus.org>
Lars Ingebrigtsen writes:
> Stefan Kangas <stefan@marxist.se> writes:
>
>> ** Manuals
>> Check for node names using problematic characters:
>> find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} +
>> Sadly makeinfo does not warn about such characters.
>>
>> Running that gives me some matches:
[...]
>> doc/misc/org.texi:@node Hooks (2)
>
> And in the Org manual, so I've added Kyle to the CCs, too.
Hmm, that "(2)" is being added by ox-texinfo.el's to make the node
unique. As I mentioned in another message
(<87tufue02l.fsf@kyleam.com>), I think these parentheses are probably
okay, even for older versions of Texinfo.
On the other hand, I have no objections to sidestepping the issue with
something like this:
diff --git a/doc/misc/org.org b/doc/misc/org.org
index 85117714ee9..adf24da1c3f 100644
--- a/doc/misc/org.org
+++ b/doc/misc/org.org
@@ -15571,7 +15571,7 @@ ** Advanced Export Configuration
:DESCRIPTION: Fine-tuning the export output.
:END:
-*** Hooks
+*** Export hooks
:PROPERTIES:
:UNNUMBERED: notoc
:END:
@@ -18203,7 +18203,7 @@ *** Functions
#+kindex: C-c C-v f
Choose a file to tangle. Bound to {{{kbd(C-c C-v f)}}}.
-*** Hooks
+*** Tangle hooks
:PROPERTIES:
:UNNUMBERED: notoc
:END:
next prev parent reply other threads:[~2021-11-30 4:39 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
2021-11-30 4:39 ` Kyle Meyer [this message]
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=87sfvedzok.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=52126@debbugs.gnu.org \
--cc=info@protesilaos.com \
--cc=larsi@gnus.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).