From: Stephen Berman <Stephen.Berman@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: minibuffer and current-local-map
Date: Thu, 08 Nov 2007 08:20:54 +0100 [thread overview]
Message-ID: <873avh2ofd.fsf@escher.local.home> (raw)
In-Reply-To: E1IpzDt-00082X-P9@fencepost.gnu.org
On Wed, 07 Nov 2007 23:42:33 -0500 Richard Stallman <rms@gnu.org> wrote:
> The value returned by current-local-map for the minibuffer
>
> Inside which command? What function was used to invoke the
> minibuffer? What map did it specify?
I noticed this after typing `M-x', thus activating the minibuffer, and
there typing C-down-mouse-3, popping up the confusing context menu seen
in the screen shots attached to my OP. C-down-mouse-3 invokes
mouse-popup-menubar-stuff, which calls mouse-major-mode-menu, which
calls current-local-map.
> seems to be
> wrong (both in the trunk and in Emacs 22.1), containing partial
> reduplication:
>
> Is the duplication present in the map that was passed as an argument
> for use in the minibuffer?
I'm not sure what you mean by "passed as an argument" here. I saw the
value of current-local-map that I posted when I stepped through
mouse-major-mode-menu with edebug. I also got this value by doing the
following (is step 4 an instance of passing the map as an argument for
use in the minibuffer?):
1. emacs -Q
2. M-: (setq enable-recursive-minibuffers t) RET
3. M-x
4. M-: (current-local-map) RET
Steve Berman
next prev parent reply other threads:[~2007-11-08 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 16:30 minibuffer and current-local-map Stephen Berman
2007-11-08 4:42 ` Richard Stallman
2007-11-08 7:20 ` Stephen Berman [this message]
2007-11-08 23:37 ` Richard Stallman
2007-11-09 22:00 ` Richard Stallman
2007-11-30 16:42 ` Jason Rumney
2007-11-30 23:36 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2008-01-06 19:36 Glenn Morris
2008-01-07 11:31 ` Richard Stallman
2008-01-07 12:43 ` Stephen Berman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873avh2ofd.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.