From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: doc of prompt change with minor mode for read-key-sequence?
Date: Mon, 18 Sep 2006 08:38:59 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMEEHCCLAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1GPKZQ-0001oS-CK@fencepost.gnu.org>
It is the map for a global minor mode, Icicles. It
functions as a menu-bar
menu map, and there are also keyboard sequences bound in it.
To make the menu-bar menu work, you need to give a prompt string aka
menu name to the map that you put on the prefix key menu-bar.
But you don't
need to give a prompt string aka menu name to the overall keymap for
Icicles. That never needs to operate as a menu.
So try removing the arg to make-sparse-keymap when you make the
overall keymap, and see if everything works right.
Thank you; that took care of it.
I think maybe I used the name in the call to `make-sparse-keymap' because I
figured it wouldn't hurt, and I might use it someday as a pop-up-menu
(somehow). This part of the doc string might have given me that impression:
"The optional arg string supplies a menu name for the keymap
in case you use it as a menu with `x-popup-menu'."
I think I figured "in case you use it" meant that it would only be used in
that case, and I didn't know at the time whether I might use it in that way
in some context. Actually, I don't really remember. Anyway, thanks. I know
now that I should reserve supplying the name for when I really want a menu.
next prev parent reply other threads:[~2006-09-18 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 16:27 doc of prompt change with minor mode for read-key-sequence? Drew Adams
2006-09-13 15:10 ` Richard Stallman
2006-09-13 15:42 ` Drew Adams
2006-09-13 16:45 ` Stefan Monnier
2006-09-13 17:19 ` Drew Adams
2006-09-13 17:58 ` Stefan Monnier
2006-09-14 2:34 ` Richard Stallman
2006-09-14 15:09 ` Drew Adams
2006-09-18 14:58 ` Richard Stallman
2006-09-18 15:38 ` Drew Adams [this message]
2006-09-18 23:39 ` Richard Stallman
2006-09-22 19:21 ` Stefan Monnier
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=EIENLHALHGIMHGDOLMIMEEHCCLAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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.
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).