From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 44858@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#44858: [PATCH] Make byte-compiler warn about wide docstrings
Date: Fri, 27 Nov 2020 10:36:50 -0800 (PST) [thread overview]
Message-ID: <a9cc658b-28c9-40a8-b69c-f67ba3efe208@default> (raw)
In-Reply-To: <87pn3zjivc.fsf@gnus.org>
> Yup. And 15% is mostly when it expands to `M-x some-long-command'
> because the keymap hasn't been loaded yet, I think? Which we could
> conceivably fix by loading the file when the used `C-h f's an
> autoloaded function with one of these constructs? Perhaps a bit hacky...
Please, no. Users should be able to see the doc
without loading the library. That's an important
feature, IMO, which has been present from Day One
(or whatever day autoloading was introduced).
I'm all for cosmetic improvements and not having
long lines, believe me. But I think loading a
library just to (maybe!) change `M-x function-name'
to a key binding description is, I think, misguided.
next prev parent reply other threads:[~2020-11-27 18: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
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 [this message]
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=a9cc658b-28c9-40a8-b69c-f67ba3efe208@default \
--to=drew.adams@oracle.com \
--cc=44858@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).