From: Eli Zaretskii <eliz@gnu.org>
To: Damien Cassou <damien@cassou.me>
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 08:04:28 +0300 [thread overview]
Message-ID: <83a5ty1smb.fsf@gnu.org> (raw)
In-Reply-To: <87edjbp1aq.fsf@cassou.me> (message from Damien Cassou on Wed, 06 Sep 2023 21:08:29 +0200)
> From: Damien Cassou <damien@cassou.me>
> Date: Wed, 06 Sep 2023 21:08:29 +0200
>
> I have this piece of code:
>
> (cl-defstruct (json-process-client-application
> (:constructor json-process-client--application-create)
> (:conc-name json-process-client--application-))
> message-callbacks)
>
> In GNU Emacs 29.1, "Warning: docstring wider than 80 characters" even
> though I wrote no docstring here. I understand the problem lies in the
> generated code and I agree the lisp names in my code are long. But, I
> don't think the byte compiler should annoy me about docstrings I didn't
> write.
>
> What do you think?
How else will we/you know there's a potential problem there?
If you think you can do nothing about this problem, just ignore the
warning. It's just a warning.
next prev parent reply other threads:[~2023-09-07 5:04 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 [this message]
2023-09-07 9:30 ` Damien Cassou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a5ty1smb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65790@debbugs.gnu.org \
--cc=damien@cassou.me \
/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.