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: Fri, 11 Dec 2020 14:36:33 -0600 [thread overview]
Message-ID: <CADwFkmnJVibHfN9=983D6vgCxhAU29uhMwTetnW4eV9dhfiAPw@mail.gmail.com> (raw)
In-Reply-To: <83mtyk3ig4.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> I'm assuming we don't want to push this without fixing those warnings,
>> so I would really appreciate some help with the remaining couple of
>> warnings.
>
> Please show those problematic doc strings, and I will try to fix them.
Thanks, I appreciate the help. Please see the below list that should be
easy to just put in a compilation-mode buffer.
gnus/deuglify.el:252:1: Warning: custom-declare-variable
`gnus-outlook-deuglify-unwrap-stop-chars' docstring wider than 80
characters
gnus/deuglify.el:259:1: Warning: custom-declare-variable
`gnus-outlook-deuglify-no-wrap-chars' docstring wider than 80 characters
gnus/deuglify.el:265:1: Warning: custom-declare-variable
`gnus-outlook-deuglify-attrib-cut-regexp' docstring wider than 80
characters
gnus/gnus.el:1529:1: Warning: custom-declare-variable
`gnus-group-charset-alist' docstring wider than 80 characters
gnus/nnvirtual.el:63:1: Warning: defvar `nnvirtual-mapping-table' docstring
wider than 80 characters
gnus/nnvirtual.el:66:1: Warning: defvar `nnvirtual-mapping-offsets' docstring
wider than 80 characters
gnus/nnvirtual.el:72:1: Warning: defvar `nnvirtual-mapping-reads' docstring
wider than 80 characters
gnus/nnvirtual.el:75:1: Warning: defvar `nnvirtual-mapping-marks' docstring
wider than 80 characters
gnus/nnvirtual.el:78:1: Warning: defvar `nnvirtual-info-installed' docstring
wider than 80 characters
language/ethio-util.el:122:1: Warning: defvar `ethio-quote-vowel-always'
docstring wider than 80 characters
language/ethio-util.el:127:1: Warning: defvar `ethio-W-sixth-always' docstring
wider than 80 characters
mail/feedmail.el:624:1: Warning: custom-declare-variable
`feedmail-sendmail-f-doesnt-sell-me-out' docstring wider than 80
characters
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
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
org/org-ctags.el:164:1: Warning: custom-declare-variable
`org-ctags-open-link-functions' docstring wider than 80 characters
org/org-protocol.el:166:1: Warning: custom-declare-variable
`org-protocol-project-alist' docstring wider than 80 characters
vc/ediff-init.el:556:1: Warning: custom-declare-variable
`ediff-before-flag-bol' docstring wider than 80 characters
vc/ediff-init.el:562:1: Warning: custom-declare-variable
`ediff-after-flag-eol' docstring wider than 80 characters
vc/ediff-init.el:568:1: Warning: custom-declare-variable
`ediff-before-flag-mol' docstring wider than 80 characters
progmodes/cc-engine.el:183:1: Warning: defvar `c-vsemi-status-unknown-p-fn'
docstring wider than 80 characters
next prev parent reply other threads:[~2020-12-11 20:36 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 [this message]
2020-12-19 11:22 ` Eli Zaretskii
2020-12-19 16:50 ` Stefan Kangas
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
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='CADwFkmnJVibHfN9=983D6vgCxhAU29uhMwTetnW4eV9dhfiAPw@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 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).