From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, 23129@debbugs.gnu.org
Subject: bug#23129: 25.1.50; Prefix key is not echoed during minibuffer completion
Date: Fri, 8 Apr 2016 08:56:09 -0700 (PDT) [thread overview]
Message-ID: <c721be46-33f1-43e3-95f4-506235830d8c@default> (raw)
In-Reply-To: <a149b774-6fbe-481e-8b6e-bda7d285a055@default>
Having just noticed the merge message for bugs 22825 and
23240, and looking at the bug descriptions, it seems to me
that both of them are essentially the same bug as this one,
23129, although this one is echoing during minibuffer input
and that one is about input during key reading. (That one
is not about just `C-h c'.)
And really the problem is more general than either of these
bug descriptions. It is not just about prefix-key echoing
being dropped during minibuffer completion. And it is not
just about it being dropped during key reading.
It is about prefix-key echoing being dropped when expecting
some input from the user. The user has hit a prefix key
and that is not getting echoed. The user gets no feedback.
I recognize that minibuffer reading of input is different,
in terms of implementation, from key reading (reading an
event). But the user need is the same in these cases:
a prefix key should be echoed, so the user knows what
key s?he hit and knows what Emacs understood and expects.
next prev parent reply other threads:[~2016-04-08 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` bug#23129: 25.1.50; Prefix key is not echoed during minibuffer completion Drew Adams
2016-04-08 15:56 ` Drew Adams [this message]
2016-04-08 16:03 ` Eli Zaretskii
[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
2016-03-27 22:34 Drew Adams
2016-03-28 15:21 ` 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=c721be46-33f1-43e3-95f4-506235830d8c@default \
--to=drew.adams@oracle.com \
--cc=23129@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).