From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Command remapping and the delete-frame problem.
Date: 24 Feb 2002 01:41:11 +0100 [thread overview]
Message-ID: <5xr8nb4spk.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200202232019.g1NKJaY14614@aztec.santafe.edu>
Richard Stallman <rms@gnu.org> writes:
> Are you now saying that remapping should have been implemented
> using a specific `command' prefix like this:
>
> (define-key map [command command1] 'command2)
>
> I am not sure about that. I was talking about what should go in the
> keymap data structure.
I have just reworked my original patch for command remapping to use
a `remap' prefix-key for command remapping:
(define-key map [remap command1] 'command2)
Please read the updated section in NEWS.
This removes the ambiguity between commands and event symbols,
and it has the added bonus of removing some of the limitations
on the previous implementation. Specifically, a command can now be
remapped into anything accepted by define-key (not just another
command). I think the new method is much cleaner.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-24 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5x3czwjqxs.fsf@kfs2.cua.dk>
[not found] ` <7263-Wed20Feb2002194728+0200-eliz@is.elta.co.il>
[not found] ` <5xd6yzwxs8.fsf@kfs2.cua.dk>
[not found] ` <200202220433.g1M4XP414080@aztec.santafe.edu>
[not found] ` <5xd6yx965v.fsf_-_@kfs2.cua.dk>
2002-02-22 15:40 ` Command remapping and the delete-frame problem Kim F. Storm
2002-02-22 16:24 ` Stefan Monnier
2002-02-22 19:31 ` Kim F. Storm
2002-02-22 19:38 ` Stefan Monnier
2002-02-23 20:19 ` Richard Stallman
2002-02-24 0:41 ` Kim F. Storm [this message]
2002-03-03 17:25 ` Tak Ota
2002-03-04 23:41 ` Richard Stallman
2002-03-05 6:19 ` Tak Ota
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=5xr8nb4spk.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--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.