From: Elena <egarrulo@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Scanning keymaps for keybindings
Date: Wed, 10 Nov 2010 11:41:20 -0800 (PST) [thread overview]
Message-ID: <185f33b3-988c-4ea9-ac2e-9d276e0c8017@s4g2000yql.googlegroups.com> (raw)
In-Reply-To: jwv4obpqczb.fsf-monnier+gnu.emacs.help@gnu.org
On Nov 10, 6:56 pm, Stefan Monnier <monn...@iro.umontreal.ca> wrote:
> I think you're going about it in the wrong way. If you tell us more
> precisely what you're trying to do, we can probably give you some better
> indications of how to do it.
Nevermind. My understanding now is that the only effective way is
tracking down by hand where the key are bound and write the
appropriate fix on a case by case basis.
However, for the curious, here is the full story. Being a Viper
+Vimpulse user, I'm used to J and K to go to next and to previous
line. For the sake of consistency, I'd like to use M-j and M-k
instead of M-p (ido-prev-work-directory) and M-n (ido-next-work-
directory) to go back and forth in IDO's (ido.el) directory history.
Of course, since N-based and P-based bindings for next and previous
items are pervasive in Emacs (for consistency) this meant I had to do
quite a few remappings. This raised the learning challenge to
somewhat automate the task.
prev parent reply other threads:[~2010-11-10 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f63f2762-b0c0-45d4-a421-ca1fc1911fc4@a9g2000pro.googlegroups.com>
2010-11-09 20:37 ` Scanning keymaps for keybindings despen
[not found] ` <f7cba2f3-7cc9-4b6e-a62a-53fb6bae8aa6@u10g2000yqk.googlegroups.com>
2010-11-09 21:31 ` despen
[not found] ` <87c203d6-9a60-494e-8652-a5d47151b0ae@u10g2000yqk.googlegroups.com>
[not found] ` <8739rab1qf.fsf@fh-trier.de>
2010-11-09 22:17 ` Elena
[not found] ` <87eiaucgpf.fsf@puma.rapttech.com.au>
2010-11-09 22:10 ` Elena
[not found] ` <87oc9yf4bo.fsf@kuiper.lan.informatimago.com>
2010-11-10 11:08 ` Elena
[not found] ` <jwv4obpqczb.fsf-monnier+gnu.emacs.help@gnu.org>
2010-11-10 19:41 ` Elena [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=185f33b3-988c-4ea9-ac2e-9d276e0c8017@s4g2000yql.googlegroups.com \
--to=egarrulo@gmail.com \
--cc=help-gnu-emacs@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.
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).