From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Problem: Keymap not working...
Date: Mon, 07 Feb 2005 13:37:00 -0700 [thread overview]
Message-ID: <36q1rcF5493j4U2@individual.net> (raw)
In-Reply-To: <36promF53us79U1@individual.net>
Kevin Rodgers wrote:
> You need to return the keymap from the let form, so that it is bound to
> the variable. Also, it's not a bug but it is a little confusing to use
> the name of the global variable as the name of the local variable:
>
> (defvar musman-mode-map
> (let ((map (make-sparse-keymap)))
> (define-key musman-mode-map "\C-ck" 'musman-Konzert)
> ...
> (define-key musman-mode-map "\C-c z" 'musman-Zur?ckrufen)
> map))
Oops, that should be:
(defvar musman-mode-map
(let ((map (make-sparse-keymap)))
(define-key map "\C-ck" 'musman-Konzert)
...
(define-key map "\C-c z" 'musman-Zur?ckrufen)
map))
--
Kevin Rodgers
next prev parent reply other threads:[~2005-02-07 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 17:36 Problem: Keymap not working upro
2005-02-06 19:49 ` Neon Absentius
2005-02-07 18:53 ` Kevin Rodgers
2005-02-07 20:37 ` Kevin Rodgers [this message]
[not found] ` <mailman.1043.1107720238.2841.help-gnu-emacs@gnu.org>
2005-03-02 15:59 ` David Combs
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=36q1rcF5493j4U2@individual.net \
--to=ihs_4664@yahoo.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).