From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, 62320@debbugs.gnu.org
Subject: bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs")
Date: Sat, 22 Jul 2023 23:01:08 -0400 [thread overview]
Message-ID: <E1qNPLI-0003ta-H5@fencepost.gnu.org> (raw)
In-Reply-To: <83o7k524ku.fsf@gnu.org> (message from Eli Zaretskii on Fri, 21 Jul 2023 08:53:21 +0300)
[[[ 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. ]]]
> If the node enumerates a long-enough list of actions or checks that
> belong to the same procedure, breaking it into several nodes makes the
> reading harder.
Splitting a node doesn't have to be done in the simplest way. In a
case like that, you can divide the actions into categories (purposes?)
that meaningfully belong together, then write a subnode for each
purpose. This offers a chance to explain them together, which is
often very helpful.
I've done this sort of thing many times, and I aim for 50 lines or
even less.
Give it a try!
--
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-23 3:01 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 [this message]
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=E1qNPLI-0003ta-H5@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.