From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Van L <van@scratch.space>, 31576@debbugs.gnu.org
Subject: bug#31576: emacs-lisp-intro.texi - NAME, TITLE inconsistency among @node, @unnumberedsec
Date: Sun, 6 Oct 2019 06:33:49 +0200 [thread overview]
Message-ID: <CADwFkmmnOMoLm7TxEg4aFtoEcb-SYZqd_BuVzb=FNGhrX8KaBQ@mail.gmail.com> (raw)
In-Reply-To: <A6DC5A21-2052-440F-941F-BD4AB3A78BC3@scratch.space>
tags 31576 + wontfix
close 31576
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Van L <van@scratch.space>
>> Date: Thu, 24 May 2018 10:41:55 +1000
>>
>> Hello.
>>
>> IMO, having `@node NAME' consistent with `@unnumberedsec TITLE' is better in an intro.
>
> I'm not sure I understand why. This is an introduction to Emacs Lisp,
> not to Texinfo. All our manuals use different names for nodes and for
> corresponding chapters/sections, primarily because the node name is
> just a label, and also because some characters should not appear ion a
> node name.
>
> I see no problem here.
Having read the discussion, and in the interest of not keeping bug
reports open that we will not want to work on, I'm closing this as
wontfix.
If anyone thinks that's the wrong thing to do, feel free reopen the bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-10-06 4:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 0:41 bug#31576: emacs-lisp-intro.texi - NAME, TITLE inconsistency among @node, @unnumberedsec Van L
2018-05-24 2:38 ` Eli Zaretskii
2018-05-24 2:47 ` Van L
2018-05-24 4:35 ` Eli Zaretskii
2018-05-24 11:51 ` Van L
2018-05-24 15:33 ` Eli Zaretskii
2018-05-26 4:32 ` Van L
2018-05-24 3:33 ` Van L
2018-05-24 4:29 ` Eli Zaretskii
2019-10-06 4:33 ` Stefan Kangas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmmnOMoLm7TxEg4aFtoEcb-SYZqd_BuVzb=FNGhrX8KaBQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=31576@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=van@scratch.space \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.