From: Drew Adams <drew.adams@oracle.com>
To: 28074@debbugs.gnu.org
Subject: bug#28074: 25.2; `Info-toc' should not duplicate nodes by processing `The Detailed Node Listing'
Date: Sat, 12 Aug 2017 19:49:50 -0700 (PDT) [thread overview]
Message-ID: <9520c346-d35a-4fcb-a83f-61f731c11721@default> (raw)
emacs -Q
C-h i
Go to the Elisp manual or the Emacs manual. Each of these has a menu of
nodes followed by a section called "The Detailed Node Listing".
M-x Info-toc
The result is not just a hierarchical TOC of the manual's nodes. The
result duplicates both the menu (hierarchical) structure AND the flat,
"Detailed Node List". The "Detailed Node List" lists each node multiple
times, once at the top level and once under each of its ancestor nodes.
This produces a TOC that is more than twice as big as it should be. But
more importantly, the result of processing the "Detailed Node List" part
is an almost incomprehensible list of links, with a great deal of
redundancy.
For example, the node `A Sample Function Description' appears 4 times:
1. In the hierarchical menu listing, under `Format of Descriptions',
which is under `Conventions', which is under `Introduction' (at the
top level).
2. In the detailed listing, under `Format of Descriptions', which is
under `Conventions' (at the top level).
3. In the detailed listing, under `Format of Descriptions' (at the top
level).
4. In the detailed listing, at the top level.
Only the first of these occurrences of `A Sample Function Description'
is needed for a TOC. And as you move further down the TOC entries and
their contexts become less readable.
In GNU Emacs 25.2.1 (x86_64-w64-mingw32)
of 2017-04-24
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --without-dbus --without-compress-install 'CFLAGS=-O2
-static -g3''
next reply other threads:[~2017-08-13 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 2:49 Drew Adams [this message]
2020-12-12 12:33 ` bug#28074: 25.2; `Info-toc' should not duplicate nodes by processing `The Detailed Node Listing' Lars Ingebrigtsen
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=9520c346-d35a-4fcb-a83f-61f731c11721@default \
--to=drew.adams@oracle.com \
--cc=28074@debbugs.gnu.org \
/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.