unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Protesilaos Stavrou <info@protesilaos.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52126@debbugs.gnu.org, larsi@gnus.org,
	Stefan Kangas <stefan@marxist.se>,
	kyle@kyleam.com, rgm@gnu.org
Subject: bug#52126: Problematic characters in info node names
Date: Mon, 29 Nov 2021 20:04:37 +0200	[thread overview]
Message-ID: <877dcqn8i2.fsf@protesilaos.com> (raw)
In-Reply-To: <83ee6yvog6.fsf@gnu.org>

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

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





  reply	other threads:[~2021-11-29 18:04 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 [this message]
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
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=877dcqn8i2.fsf@protesilaos.com \
    --to=info@protesilaos.com \
    --cc=52126@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kyle@kyleam.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).