From: Stefan Kangas <stefankangas@gmail.com>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 72357@debbugs.gnu.org
Subject: bug#72357: Checkdoc fixes in transient.el
Date: Sat, 14 Sep 2024 06:40:58 -0700 [thread overview]
Message-ID: <CADwFkmnknpMFTo4PQyHB=BzHv094BA8=gMrEtXrME6BCH6iW5Q@mail.gmail.com> (raw)
In-Reply-To: <87a5hzn9qn.fsf@bernoul.li>
Jonas Bernoulli <jonas@bernoul.li> writes:
> Looking at, for example, "C-h f transient-format-description", I feel
> that it would not make sense if all the methods themselves began with a
> summary line. Only the overall generic function *needs* a summary line.
> In some case it may make sense to give individual methods their own
> summary lines, but for very short, one paragraph method docstrings this
> should not be a requirements. When a method is so simple that it can be
> described using a single short paragraph (but not a single sentence,
> which can fit on a single line), then that should be possible, without
> being forced to mess up the justification of that paragraph.
Sure, I understand your reasoning. I don't know if this needs pointing
out, but do feel free to revert these changes.
Meanwhile, Eli has proposed a rewording of the docstring that you might
want to look at.
> IMO checkdoc should be updated to not enforce the conventions, which
> were designed for "top-level" functions (and variables) on methods
> as well.
Makes sense to me.
BTW, with debbugs, it's better to put people in the "X-Debbugs-CC"
header than "Cc". That way, I get the email forwarded to me by the bug
tracker, and when I hit "wide reply", I send it to the right bug
automatically (I had to edit in manually here).
prev parent reply other threads:[~2024-09-14 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 21:56 bug#72357: Checkdoc fixes in transient.el Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-30 11:39 ` Eli Zaretskii
2024-09-14 13:40 ` Stefan Kangas [this message]
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='CADwFkmnknpMFTo4PQyHB=BzHv094BA8=gMrEtXrME6BCH6iW5Q@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=72357@debbugs.gnu.org \
--cc=jonas@bernoul.li \
/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).