From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
emacs-devel@gnu.org, ponced16@netscape.net (David Ponce)
Subject: Re: Old CUA and new keyboard.c (was: Problem with latest CVS version of keyboard.c (solved) )
Date: Fri, 14 Jun 2002 11:14:05 -0400 [thread overview]
Message-ID: <200206141514.g5EFE5Y30014@rum.cs.yale.edu> (raw)
In-Reply-To: 5xofeehhgd.fsf@kfs2.cua.dk
> > > > I was wondering why you need to wait for the next character after a
> > > > C-x or C-c to see if they start a function key... I don't think those
> > > > specific keys will ever do that, so maybe you should only delay the
> > > > use of key-translation-map in case the key is actually a potential
> > > > candidate for starting a function key.
> > >
> > > That sounds like a good approach. I'll see what I can do with it.
> >
> > Actually, C-x is already bound in function-key-map in the dumped
> > Emacs because of the `C-x @ m', `C-x @ a', ... feature.
>
> So in the future, we cannot remap [C-x] through key-translation-map.
Of course we can. It's just that the remapping takes place late:
not when you hit C-x but only after you've hit C-x C-f.
So I guess you're right that we cannot remap just [?\C-x], but
we can only remap [?\C-x ...] to [<somethingelse> ...].
Hmmm...
Stefan
prev parent reply other threads:[~2002-06-14 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 14:33 Problem with latest CVS version of keyboard.c (solved) David Ponce
2002-06-12 15:19 ` Old CUA and new keyboard.c (was: Problem with latest CVS version of keyboard.c (solved) ) Stefan Monnier
2002-06-12 22:06 ` Kim F. Storm
2002-06-12 22:31 ` Stefan Monnier
2002-06-12 23:49 ` Stefan Monnier
2002-06-13 5:29 ` Eli Zaretskii
2002-06-13 23:45 ` Kim F. Storm
2002-06-13 23:44 ` Kim F. Storm
2002-06-14 15:14 ` Stefan Monnier [this message]
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=200206141514.g5EFE5Y30014@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=ponced16@netscape.net \
/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).