From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, Richard Stallman <rms@gnu.org>
Cc: 23129@debbugs.gnu.org
Subject: bug#23129: 25.1.50; Prefix key is not echoed during minibuffer completion
Date: Mon, 28 Mar 2016 18:21:26 +0300 [thread overview]
Message-ID: <83shzay6fd.fsf@gnu.org> (raw)
In-Reply-To: <e28dfa52-d2e2-40ae-80e2-112b30cdad25@default> (message from Drew Adams on Sun, 27 Mar 2016 15:34:02 -0700 (PDT))
> Date: Sun, 27 Mar 2016 15:34:02 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> 0. emacs -Q
>
> 1.
> (defvar bar-map nil)
> (define-prefix-command 'bar-map)
> (define-key minibuffer-local-must-match-map "\M-i" 'bar-map)
> (define-key bar-map "\M-z" 'foo)
> (defun foo () (interactive) (message "FOOOOOOOOOOO") (sleep-for 2))
>
> `M-x M-i'
> Wait a second. The prefix key `M-i' is NOT echoed.
> `M-z'
> The message from `foo' is shown.
>
> 2.
> (global-set-key "\M-l" 'bar-map)
>
> `M-l'
> Wait a second. The prefix key `M-l' IS echoed.
> `M-z'
> The message from `foo' is shown.
Is it really necessary to use this complex setup? Does the following
simple recipe exhibit the same behavior? (If not, please tell why
not.)
emacs -Q
C-x C-f C-x
"C-x C-f" causes the prompt showing the current directory; typing
"C-x" afterwards has no visible effect, whereas you expect it to echo
the usual "C-x-". Right?
> BUG: The prefix key `M-i' should be echoed during completion.
How do you mean "should"? AFAICT, this is a deliberate feature: we
only echo the prefix keys when there's nothing in the minibuffer (more
accurately, when the minibuffer level of recursion is zero). I guess
this is so to avoid confusing prompts or something (Richard, can you
comment on this?), but in any case this is how Emacs worked since
forever.
next prev parent reply other threads:[~2016-03-28 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 22:34 bug#23129: 25.1.50; Prefix key is not echoed during minibuffer completion Drew Adams
2016-03-28 15:21 ` Eli Zaretskii [this message]
[not found] <<e28dfa52-d2e2-40ae-80e2-112b30cdad25@default>
[not found] ` <<83shzay6fd.fsf@gnu.org>
2016-03-28 16:00 ` Drew Adams
2016-03-28 16:16 ` Eli Zaretskii
2022-01-24 11:07 ` Lars Ingebrigtsen
[not found] <<<e28dfa52-d2e2-40ae-80e2-112b30cdad25@default>
[not found] ` <<<83shzay6fd.fsf@gnu.org>
[not found] ` <<5a83c42d-50c1-4217-b1dd-506814a7ed34@default>
[not found] ` <<83io06y3vi.fsf@gnu.org>
2016-03-28 17:32 ` Drew Adams
2016-04-08 15:56 ` Drew Adams
2016-04-08 16:03 ` Eli Zaretskii
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=83shzay6fd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23129@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=rms@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).