From: Michael Albinus <michael.albinus@gmx.de>
To: Richard Stallman <rms@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
eliz@gnu.org, 62320@debbugs.gnu.org
Subject: bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs")
Date: Fri, 21 Jul 2023 09:55:45 +0200 [thread overview]
Message-ID: <87bkg5em0u.fsf@gmx.de> (raw)
In-Reply-To: <E1qMg5i-0003SD-5L@fencepost.gnu.org> (Richard Stallman's message of "Thu, 20 Jul 2023 22:42:02 -0400")
Richard Stallman <rms@gnu.org> writes:
Hi,
> When a node is very long, that doesn't mean we should leave out
> something useful. Rather, it suggests we should split it up into
> several shorter nodes.
>
> Info's navigation is helpful when nodes are reasonable in size.
> For long nodes, they are less helpful because they don't help
> users find interesting _parts_ of a long node.
In my texinfo files, I use @anchor inside long nodes. This allows better
references to specific information in that node.
See for example (info "(tramp)Quick Start Guide sudoedit method")
Best regards, Michael.
next prev parent reply other threads:[~2023-07-21 7:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 5:23 bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs") Michael Heerdegen
2023-03-21 14:21 ` Eli Zaretskii
2023-03-22 2:21 ` Michael Heerdegen
2023-03-23 13:34 ` Eli Zaretskii
2023-03-29 15:19 ` Michael Heerdegen
2023-03-29 15:52 ` Eli Zaretskii
2023-03-30 16:08 ` Michael Heerdegen
2023-04-01 10:02 ` Eli Zaretskii
2023-07-20 2:26 ` Michael Heerdegen
2023-07-20 5:02 ` Eli Zaretskii
2023-07-21 2:42 ` Richard Stallman
2023-07-21 5:53 ` Eli Zaretskii
2023-07-23 3:01 ` Richard Stallman
2023-07-21 7:55 ` Michael Albinus [this message]
2023-07-23 3:01 ` Richard Stallman
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=87bkg5em0u.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=62320@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=rms@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 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).