From: Richard Stallman <rms@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: eliz@gnu.org, 62320@debbugs.gnu.org
Subject: bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs")
Date: Thu, 20 Jul 2023 22:42:02 -0400 [thread overview]
Message-ID: <E1qMg5i-0003SD-5L@fencepost.gnu.org> (raw)
In-Reply-To: <87pm4nuxlr.fsf@web.de> (message from Michael Heerdegen on Thu, 20 Jul 2023 04:26:40 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > > > > You also have worked in all my suggestions - apart from the "if
> > > > > you know how please load relevant Elisp source files before
> > > > > capturing an Elisp backtrace" one - intentionally?
> > I remember debating whether it was important enough to have in this
> > already very long node. But since now that part is near the end, as a
> > kind of "Advanced" section, I added that back.
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.
I suggest that any node over 50 lines long is a long node, so it is good
to split th enode into several nodes that are reasonable in size.
Or at least close.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2023-07-21 2:42 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 [this message]
2023-07-21 5:53 ` Eli Zaretskii
2023-07-23 3:01 ` Richard Stallman
2023-07-21 7:55 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1qMg5i-0003SD-5L@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=62320@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/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.