From: litter@graffiti.net (paul)
Subject: Re: How to translate M-kp-multiply to M-* before key is mapped to function?
Date: 6 Jul 2004 02:23:31 -0700 [thread overview]
Message-ID: <bb3e39cd.0407060123.13e88991@posting.google.com> (raw)
In-Reply-To: jwvacyenxga.fsf-monnier+gnu.emacs.help@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> wrote in message news:<jwvacyenxga.fsf-monnier+gnu.emacs.help@gnu.org>...
> > My problem is, is that kp-multiply is bound to * somewhere down the line,
> > but C-kp-multiply, M-kp-multiply and C-M-kp-multiply are not. I would
> > like C-kp-multiply to act like C-*, M-multiply to act like M-*, and
> > C-M-kp-multiply to act like C-M-* (without having to rely on information
> > to what functions C-*, M-* and C-M-* are bound).
>
> > How to tell keyboard-translate to do just this?
>
> You need something like
>
> (define-key function-key-map [M-kp-multiply] [?\M-*])
> (define-key function-key-map [C-kp-multiply] [?\C-*])
> (define-key function-key-map [C-M-kp-multiply] [?\C-\M-*])
>
> I don't think there is an easy way to have all combinations mapped in
> a single step. Sadly.
>
>
> Stefan
Hi Stefan,
Thanks for your reply. I don't mind having to do multiple steps for this.
Unfortunately, the solution you propose is the one I tried too.
It doesn't work.
Although it indeed remaps the key unto the correct key, it does *NOT* call
the function bound to that key. This is due to the order in which this
remapping is done, it happens *after* the effects of global-set-key, as
far as I can tell (at least it does for M-*, pop-tag-mark).
Regards,
Paul
next prev parent reply other threads:[~2004-07-06 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 15:10 How to translate M-kp-multiply to M-* before key is mapped to function? paul
2004-07-02 15:28 ` Kai Grossjohann
2004-07-02 16:32 ` Kevin Rodgers
2004-07-04 21:51 ` paul
2004-07-05 8:01 ` paul
2004-07-05 18:05 ` Stefan Monnier
2004-07-06 9:23 ` paul [this message]
2004-07-07 17:13 ` 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=bb3e39cd.0407060123.13e88991@posting.google.com \
--to=litter@graffiti.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.
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).