From: Eli Zaretskii <eliz@gnu.org>
To: Van L <van@scratch.space>
Cc: 31576@debbugs.gnu.org
Subject: bug#31576: emacs-lisp-intro.texi - NAME, TITLE inconsistency among @node, @unnumberedsec
Date: Thu, 24 May 2018 18:33:01 +0300 [thread overview]
Message-ID: <83muwpax1u.fsf@gnu.org> (raw)
In-Reply-To: <AA81560A-BD56-4C4B-AA60-3AC98F73815D@scratch.space> (message from Van L on Thu, 24 May 2018 21:51:59 +1000)
> From: Van L <van@scratch.space>
> Date: Thu, 24 May 2018 21:51:59 +1000
> Cc: 31576@debbugs.gnu.org
>
> : d6adf7e7 (Glenn Morris 2012-05-28 1206) @node Typing Lists
> : 8cda6f8f (Glenn Morris 2007-09-06 1207) @subsection GNU Emacs Helps You Type Lists
>
> it makes sense why the node name is short, presentation-wise in the infopage.
Yes, that's one of the aspects of a good Texinfo usage.
> A comment saying this is justified at the first instance will help future readers in the texi file.
I don't think this manual is a place to document that. How to choose
good node names is explained in the Texinfo manual, see the node "Node
Names" there.
This manual should (as any other manual, IMO) assume the typical
reader reads it either in Info/HTML, or in PDF, or as a book. the
Texinfo source is not the medium whose appearance we should judge wrt
these aspects.
next prev parent reply other threads:[~2018-05-24 15: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 [this message]
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
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=83muwpax1u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31576@debbugs.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.