From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: Sparse key maps garbage?
Date: Sun, 31 Aug 2008 01:44:10 +0200 [thread overview]
Message-ID: <48B9DB4A.5010203@gmail.com> (raw)
If you do
(defvar my-sparse-map (make-sparse-keymap))
(define-key my-sparse-map [f4] nil)
then there will be an entry with f4 in my-sparse-keymap. I do not think
that is used for anything. Is it? Should it be there?
next reply other threads:[~2008-08-30 23:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 23:44 Lennart Borgman (gmail) [this message]
2008-08-31 6:18 ` Sparse key maps garbage? Stefan Monnier
2008-08-31 12:17 ` Lennart Borgman (gmail)
2008-08-31 12:55 ` Stefan Monnier
2008-08-31 13:05 ` Lennart Borgman (gmail)
2008-08-31 18:19 ` Stefan Monnier
2008-08-31 20:09 ` Lennart Borgman (gmail)
2008-09-01 3:00 ` Stefan Monnier
2008-09-01 7:34 ` Lennart Borgman (gmail)
2008-09-01 18:25 ` Stefan Monnier
2008-09-01 22:28 ` Lennart Borgman (gmail)
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=48B9DB4A.5010203@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).