From: Juri Linkov <juri@linkov.net>
To: Stefan Kangas <stefan@marxist.se>
Cc: 52523@debbugs.gnu.org
Subject: bug#52523: 29.0.50; defcustom :type 'key-sequence not following key-valid-p format
Date: Thu, 16 Dec 2021 19:11:36 +0200 [thread overview]
Message-ID: <865yroa7l7.fsf@mail.linkov.net> (raw)
In-Reply-To: <CADwFkm=bxee2NA5tQPuKN681VW=kSWkXCHExnsh-ivNaPVaUDg@mail.gmail.com> (Stefan Kangas's message of "Wed, 15 Dec 2021 12:35:03 -0800")
> Now that we prefer the key-valid-p format, we should think about what to
> do about defcustom as well. We currently have that:
>
> (defcustom foo "C-a" "" :type 'key-sequence)
>
> Followed by `M-x customize-option RET foo RET' leads to a customize
> buffer where this is displayed as "C - a". IOW, there is only support
> for the legacy format "\C-a".
>
> We can't just change this in a backwards incompatible way, but perhaps
> we should document it as deprecated and introduce a new format for the
> new type?
Indeed, a new type would be preferable. How about
:type 'kbd
next prev parent reply other threads:[~2021-12-16 17:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 20:35 bug#52523: 29.0.50; defcustom :type 'key-sequence not following key-valid-p format Stefan Kangas
2021-12-16 17:11 ` Juri Linkov [this message]
2021-12-19 12:15 ` Lars Ingebrigtsen
2021-12-19 13:43 ` Stefan Kangas
2021-12-19 13:54 ` Lars Ingebrigtsen
2021-12-19 17:08 ` Juri Linkov
2021-12-20 6:59 ` Stefan Kangas
[not found] ` <86tuf3ptcr.fsf@mail.linkov.net>
2021-12-20 10:27 ` Lars Ingebrigtsen
2021-12-21 11:19 ` Stefan Kangas
2021-12-21 18:53 ` Juri Linkov
2021-12-22 12:41 ` Lars Ingebrigtsen
2021-12-26 16:39 ` Stefan Kangas
2021-12-27 12:05 ` Lars Ingebrigtsen
2021-12-27 15:41 ` Stefan Kangas
2021-12-28 14:32 ` Lars Ingebrigtsen
2021-12-28 3:08 ` Stefan Kangas
2021-12-28 12:51 ` Eli Zaretskii
2021-12-28 14:33 ` Lars Ingebrigtsen
2021-12-28 14:34 ` Lars Ingebrigtsen
2022-01-02 16:00 ` Stefan Kangas
2021-12-22 4:16 ` Richard Stallman
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=865yroa7l7.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=52523@debbugs.gnu.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).