From: Stefan Kangas <stefan@marxist.se>
To: 56973@debbugs.gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#56973: :keymap in register-definition-prefixes in loaddefs
Date: Thu, 4 Aug 2022 12:16:58 +0000 [thread overview]
Message-ID: <CADwFkmm3Er0OV=Spw5iHoPk564-zN8AsnudDCCguh-OFAp2=jQ@mail.gmail.com> (raw)
Severity: minor
I see in ldefs-boot.el lines like:
(register-definition-prefixes "gnus-sum" '(":keymap" "gnus-"))
The ":keymap" there is from definitions like:
(define-keymap :keymap gnus-summary-mode-map
...)
I'm not sure what is the best fix, however. Should such cases just be
changed to use `defvar-keymap', or should we add `define-keymap' to
`autoload-ignored-definitions'?
next reply other threads:[~2022-08-04 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 12:16 Stefan Kangas [this message]
2022-08-04 13:29 ` bug#56973: :keymap in register-definition-prefixes in loaddefs Lars Ingebrigtsen
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='CADwFkmm3Er0OV=Spw5iHoPk564-zN8AsnudDCCguh-OFAp2=jQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=56973@debbugs.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).