From: Damien Cassou <damien@cassou.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65790@debbugs.gnu.org
Subject: bug#65790: 29.1; "docstring wider than 80 characters" when there is no docstring
Date: Thu, 07 Sep 2023 11:30:10 +0200 [thread overview]
Message-ID: <87il8mwct9.fsf@cassou.me> (raw)
In-Reply-To: <83a5ty1smb.fsf@gnu.org>
Hi Eli,
Eli Zaretskii <eliz@gnu.org> writes:
> How else will we/you know there's a potential problem there?
my opinion is that if more than 80 characters in a docstring is a
problem then the macro should make sure not to generate one.
> If you think you can do nothing about this problem, just ignore the
> warning. It's just a warning.
I hate warnings: either a problem is important and I want the build to
fail or there is no problem and I don't want to see anything. If I let
warnings exist then the ones I want to ignore will slowly be too
numerous for me to notice those I would like to fix.
This is why in my tool chain (makel) I'm always setting
`byte-compile-error-on-warn' to t and I do similar things in non
elisp-projects.
This is just my opinion.
Best
--
Damien Cassou
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
next prev parent reply other threads:[~2023-09-07 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 19:08 bug#65790: 29.1; "docstring wider than 80 characters" when there is no docstring Damien Cassou
2023-09-07 5:04 ` Eli Zaretskii
2023-09-07 9:30 ` Damien Cassou [this message]
2023-09-07 8:52 ` Stefan Kangas
2023-09-07 9:33 ` Damien Cassou
2023-09-07 9:47 ` Stefan Kangas
2023-09-10 6:47 ` Damien Cassou
2023-09-10 9:55 ` Stefan Kangas
2023-09-12 19:22 ` Damien Cassou
2023-09-13 14:38 ` Stefan Kangas
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=87il8mwct9.fsf@cassou.me \
--to=damien@cassou.me \
--cc=65790@debbugs.gnu.org \
--cc=eliz@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).