unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "T.V Raman" <raman@google.com>,  emacs-devel@gnu.org
Subject: Re: keymap.el and its checks
Date: Mon, 03 Oct 2022 22:57:19 +0300	[thread overview]
Message-ID: <86czb8vfz0.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwvlepxcbso.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 03 Oct 2022 08:50:10 -0400")

>> BTW, repeat-exit-key could support `kbd` format as well after changing
>> its customization type to:
>>
>>   :type '(choice (const :tag "No special key to exit repeating sequence" nil)
>>                  (string :tag "Kbd string that exits repeating sequence")
>>                  (key-sequence :tag "Key that exits repeating sequence"))
>>
>> This assumes that `key-sequence` can't be a string.
>
> `key-sequence` can definitely be a string.

This means they can be used together.  So I just replaced
`key-sequence` with `key`, and added backward-compatibility code.

>> After that you could use (key-parse repeat-exit-key) to append it
>> to unread-command-events.
>
> `key-parse` returns a ... key-sequence, so it's of no help to Raman's
> "problem".

I believe the new function repeat-exit will help Raman in another way.



  reply	other threads:[~2022-10-03 19:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03  0:39 keymap.el and its checks T.V Raman
2022-10-03  0:48 ` Stefan Monnier
2022-10-03  1:10   ` T.V Raman
2022-10-03  1:15   ` T.V Raman
2022-10-03  2:52     ` Stefan Monnier
2022-10-03  6:58 ` Juri Linkov
2022-10-03 12:50   ` Stefan Monnier
2022-10-03 19:57     ` Juri Linkov [this message]
2022-10-03 20:48       ` Stefan Monnier

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=86czb8vfz0.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=raman@google.com \
    /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).