From: Dan Bensen <randomgeek@cyberspace.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Looking for a sneaky key binding
Date: Sun, 04 Mar 2007 21:49:16 -0600 [thread overview]
Message-ID: <esg3n3$8lm$1@wildfire.prairienet.org> (raw)
In-Reply-To: <esg26u$7h4$1@wildfire.prairienet.org>
Dan Bensen wrote:
> Is kbd documented somewhere? I don't see it in the elisp or
> emacs manuals or google.
I found the description with C-h f, which led to insert-kbd-macro,
but neither entry describes the syntax of the string for the key
sequence.
Also, I'm interested in how someone is supposed to find it by themself
without having to be told about it, considering it seems pretty useful
for defining bindings.
--
Dan
www.prairienet.org/~dsb
next prev parent reply other threads:[~2007-03-05 3:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 1:09 Looking for a sneaky key binding Dan Bensen
2007-03-05 2:02 ` weber
2007-03-05 2:37 ` David Hansen
[not found] ` <mailman.438.1173062316.7795.help-gnu-emacs@gnu.org>
2007-03-05 3:23 ` Dan Bensen
2007-03-05 3:49 ` Dan Bensen [this message]
2007-03-06 13:07 ` Johan Bockgård
2007-03-06 4:44 ` Kevin Rodgers
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='esg3n3$8lm$1@wildfire.prairienet.org' \
--to=randomgeek@cyberspace.net \
--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).