From: Lennart Borgman <lennart.borgman@gmail.com>
To: LanX <lanx.perl@googlemail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: managing my keybindings
Date: Sat, 8 May 2010 04:09:21 +0200 [thread overview]
Message-ID: <x2ye01d8a51005071909i84baca91w3a0aa91ad9c7ee1e@mail.gmail.com> (raw)
In-Reply-To: <89f1a7ef-b8e5-41e9-8571-17ef186b78b4@e1g2000yqe.googlegroups.com>
On Sat, May 8, 2010 at 2:38 AM, LanX <lanx.perl@googlemail.com> wrote:
> Hi
>
> I'm looking for suggestions how to manage my keybindings.
>
> I would like to:
>
> a) list them (only *my* keybindings)
Use define-minor-mode and make a global minor mode. Define your key
bindings there.
> b) easily navigate to the place where they are defined
Define them in one place.
> c) attach documentation to them
Documentation are bound to functions, not key bindings. (You can add
comments where you bind the keys, of course.)
> d) warn me about conflicts
Use what is said in "Key binding conventions", see
M-: (info "(elisp) Key binding conventions")
> my first idea is to create wrapper functions/macros `my-global-set-
> key' and `my-local-set-key' which buffer the necessary informations
> when defining the bindings.
>
> But chances are high that I'm reinventing the wheel, so please gimme
> some ideas! 8)
>
> Cheers
> Rolf
>
> PS: another "brute force" approach would be creating an extra
> function starting with "mykey-" for every keybinding. I could list
> them by this naming convention and navigate to the files ... well not
> too elegant...
>
next prev parent reply other threads:[~2010-05-08 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 0:38 managing my keybindings LanX
2010-05-08 2:09 ` Lennart Borgman [this message]
2010-05-08 12:22 ` LanX
[not found] ` <mailman.0.1273284589.603.help-gnu-emacs@gnu.org>
2010-05-09 11:29 ` Andreas Politz
2010-05-09 11:55 ` Lennart Borgman
2010-05-09 18:21 ` LanX
2010-05-09 19:12 ` LanX
2010-05-10 14:10 ` Stefan Monnier
2010-05-10 14:25 ` LanX
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=x2ye01d8a51005071909i84baca91w3a0aa91ad9c7ee1e@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lanx.perl@googlemail.com \
/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).