all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: master 570a11052b: keymap.el: Ease up support for non-`kbd` formats.
Date: Sun, 02 Oct 2022 21:53:55 +0200	[thread overview]
Message-ID: <87y1ty80j0.fsf@gnus.org> (raw)
In-Reply-To: <jwvczbaf1ol.fsf-monnier+Inbox@gnu.org> (Stefan Monnier's message of "Sun, 02 Oct 2022 15:49:14 -0400")

(Gah, wrong address again...  I really should fix that ecomplete thing
you suggested the other week, because otherwise "emacs-devel@gnus.org"
is going to be my emacs-devel completion forever.)

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> So it makes no sense to force people through (key-parse (key-description
> <vector>)) when they have a low-level vector keysequence to start with.

The sense it makes is that `key-parse' takes one and only one syntax --
which is easy to conceptualise.  If they have a key representation in a
different format (for historical or other reasons), they should
translate that to the advertised format like that.

We've been over this before, several times.  I understand that you
disagree, but you're not saying anything new.




  parent reply	other threads:[~2022-10-02 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166473415340.3541.7915775151764125824@vcs2.savannah.gnu.org>
     [not found] ` <20221002180913.AD50AC0004A@vcs2.savannah.gnu.org>
2022-10-02 18:32   ` master 570a11052b: keymap.el: Ease up support for non-`kbd` formats Lars Ingebrigtsen
2022-10-02 19:51     ` Stefan Monnier
     [not found]   ` <87lepy9jly.fsf@gnus.org>
     [not found]     ` <jwvczbaf1ol.fsf-monnier+Inbox@gnu.org>
2022-10-02 19:53       ` Lars Ingebrigtsen [this message]
2022-10-02 20:49         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y1ty80j0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.