From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44858@debbugs.gnu.org, larsi@gnus.org
Subject: bug#44858: [PATCH] Make byte-compiler warn about wide docstrings
Date: Sat, 19 Dec 2020 10:50:33 -0600 [thread overview]
Message-ID: <CADwFkmm3n2j+nVu3WhHJ9CoOB8h++FCFaO5v-jtzCdyy8_Ty+A@mail.gmail.com> (raw)
In-Reply-To: <83wnxet4z9.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I see nothing wrong with these, so either I'm missing something or
> there's a bug in the code which reports these problems.
Thanks for the fixes. See my comments below:
>> mh-e/mh-e.el:2827:1: Warning: custom-declare-variable
>> `mh-invisible-header-fields' docstring wider than 80 characters
>> mh-e/mh-e.el:2850:1: Warning: custom-declare-variable
>> `mh-invisible-header-fields-default' docstring wider than 80 characters
AFAICT, the offending lines are the ones containing URLs:
line 2839:
`https://sourceforge.net/tracker/index.php?func=detail&aid=1916032&group_id=13357&atid=113357').
line 2683:
`https://sourceforge.net/tracker/index.php?func=detail&aid=1916032&group_id=13357&atid=113357').
I see two issues here:
a) The URL does not easily break over two lines. I'm not sure what we
should do. Add a special case to ignore lines with URLs?
b) The warning doesn't point you to the actually offending line, but to
the definition containing the docstring. I'm not sure if this is
easily fixable or not, or if it's important enough to be worth
spending time on.
>> net/dbus.el:79:1: Warning: defconst `dbus-interface-peer' docstring wider than
>> 80 characters
>> net/dbus.el:91:1: Warning: defconst `dbus-interface-introspectable' docstring
>> wider than 80 characters
>> net/dbus.el:102:1: Warning: defconst `dbus-interface-properties' docstring
>> wider than 80 characters
>> net/dbus.el:128:1: Warning: defconst `dbus-interface-objectmanager' docstring
>> wider than 80 characters
>> net/dbus.el:148:1: Warning: defconst `dbus-interface-monitoring' docstring
>> wider than 80 characters
Again we have URLs, like on line 81:
See URL `https://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-peer'."
>> org/org-protocol.el:166:1: Warning: custom-declare-variable
>> `org-protocol-project-alist' docstring wider than 80 characters
>
> I don't see a problem here.
I fixed that one.
>> progmodes/cc-engine.el:183:1: Warning: defvar `c-vsemi-status-unknown-p-fn'
>> docstring wider than 80 characters
>
> I don't see how I can do anything about this one.
I'm also stomped. Perhaps we could ask Alan for help with this one.
next prev parent reply other threads:[~2020-12-19 16:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 1:36 bug#44858: [PATCH] Make byte-compiler warn about wide docstrings Stefan Kangas
2020-11-26 10:49 ` Lars Ingebrigtsen
2020-11-26 12:46 ` Stefan Kangas
2020-11-26 12:53 ` Lars Ingebrigtsen
2020-12-10 20:59 ` Stefan Kangas
2020-12-10 21:53 ` Stefan Kangas
2020-12-11 8:16 ` Eli Zaretskii
2020-12-11 20:03 ` Stefan Kangas
2020-12-11 7:33 ` Eli Zaretskii
2020-12-11 20:36 ` Stefan Kangas
2020-12-19 11:22 ` Eli Zaretskii
2020-12-19 16:50 ` Stefan Kangas [this message]
2020-12-19 17:14 ` Eli Zaretskii
2020-12-29 1:27 ` Basil L. Contovounesios
2020-12-29 2:16 ` Lars Ingebrigtsen
2020-12-19 17:18 ` Lars Ingebrigtsen
2020-12-19 23:48 ` Stefan Kangas
2020-12-11 7:53 ` Eli Zaretskii
2020-12-19 23:55 ` Stefan Kangas
2020-12-20 17:53 ` Lars Ingebrigtsen
2020-12-28 5:18 ` Stefan Kangas
2020-12-11 15:13 ` Lars Ingebrigtsen
2020-12-30 12:07 ` Stefan Kangas
2020-12-31 4:42 ` Lars Ingebrigtsen
2020-11-26 14:19 ` Eli Zaretskii
2020-11-27 8:37 ` Lars Ingebrigtsen
2020-11-27 11:15 ` Stefan Kangas
2020-11-27 12:44 ` Eli Zaretskii
2020-12-06 11:09 ` Stefan Kangas
2020-12-06 11:19 ` Eli Zaretskii
2020-12-06 16:54 ` Drew Adams
2020-11-27 18:36 ` Drew Adams
2020-11-27 18:55 ` Drew Adams
2020-12-03 20:18 ` Tomas Nordin
2020-12-11 20:14 ` Stefan Kangas
2021-09-24 17:25 ` Stefan Kangas
2021-09-25 1:07 ` Lars Ingebrigtsen
2021-09-26 11: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=CADwFkmm3n2j+nVu3WhHJ9CoOB8h++FCFaO5v-jtzCdyy8_Ty+A@mail.gmail.com \
--to=stefan@marxist.se \
--cc=44858@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.