unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: emacs-devel@gnu.org
Subject: Re: Keymap customization
Date: Wed, 02 Oct 2002 11:30:32 +0200	[thread overview]
Message-ID: <rj7kh1tcg7.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: <E17tgJ0-0006Pg-00@fencepost.gnu.org> (Richard Stallman's message of "Mon, 23 Sep 2002 23:24:10 -0400")

Richard Stallman <rms@gnu.org> writes:

>     1. The defkeymap should generate a defvar.
>
>     2. The generation of new prefix keys is not supported.
>
>     3. We really should use a two-keymap solution in define-key.
>
>     Fixing #3 would also fix #2.
>
>     I am willing to solve #1 if that mean I can commit the code to the
>     Emacs CVS.  I'll also think about #2 then.
>
> Don't bother with doing #2 using the current data format, since #3
> will take care of it.
>
> Is anyone interested in doing #3 now?

Nobody seems to volunteer.  

So do we give up, or use Alex' implementation?

As I said, I believe Alex' implementation will be forward compatible
with a define-key based solution, and I also believe this will be the
most important single improvement for ordinary users since Emacs 21.1,
so I believe we should go ahead with Alex' code.

  reply	other threads:[~2002-10-02  9:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 10:23 Keymap customization Per Abrahamsen
2002-09-24  3:24 ` Richard Stallman
2002-10-02  9:30   ` Per Abrahamsen [this message]
2002-10-02 15:06     ` Stefan Monnier
2002-10-03 22:38       ` Kim F. Storm
2002-10-02 19:23     ` Richard Stallman
2002-10-10 13:30       ` Per Abrahamsen
2002-10-10 20:11         ` Alex Schroeder
2002-10-11 12:44           ` Richard Stallman
2002-10-11 18:04             ` Alex Schroeder
2002-10-12 13:01               ` Per Abrahamsen
2002-12-30 18:28                 ` Per Abrahamsen

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=rj7kh1tcg7.fsf@zuse.dina.kvl.dk \
    --to=abraham@dina.kvl.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 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).