From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: michael_heerdegen@web.de, 62320@debbugs.gnu.org
Subject: bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs")
Date: Fri, 21 Jul 2023 08:53:21 +0300 [thread overview]
Message-ID: <83o7k524ku.fsf@gnu.org> (raw)
In-Reply-To: <E1qMg5i-0003SD-5L@fencepost.gnu.org> (message from Richard Stallman on Thu, 20 Jul 2023 22:42:02 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: eliz@gnu.org, 62320@debbugs.gnu.org
> Date: Thu, 20 Jul 2023 22:42:02 -0400
>
> 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.
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.
But of course, I agree with the general principle. Although 50 is too
small a number, IME; I think 150 is a better limit.
next prev parent reply other threads:[~2023-07-21 5:53 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 [this message]
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=83o7k524ku.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62320@debbugs.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 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.