From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: toon@to1.studio, joaotavora@gmail.com, 62355@debbugs.gnu.org
Subject: bug#62355: 30.0.50; C-g doesn't always quit minibuffer on first press
Date: Thu, 23 Mar 2023 22:09:00 +0200 [thread overview]
Message-ID: <83sfdv44df.fsf@gnu.org> (raw)
In-Reply-To: <87zg83e032.fsf@melete.silentflame.com> (message from Sean Whitton on Thu, 23 Mar 2023 12:31:29 -0700)
> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: João Távora <joaotavora@gmail.com>
> Date: Thu, 23 Mar 2023 12:31:29 -0700
>
> I've been seeing something similar and I have a theory as to the cause.
> I am using Icomplete, and I think what happens is that the C-g
> interrupts something Icomplete is doing, rather than serving to exit the
> minibuffer. Toon, are you using Icomplete or similar?
>
> Here is my evidence. One machine on which I use Emacs is underpowered.
> With icomplete-show-matches-on-no-input non-nil, on that machine, I type
> M-x, and wait for the completions to appear. I do this several times so
> that I have an intuitive sense for how long they take to appear. And
> then I type M-x, and try to hit C-g while Icomplete is computing. I can
> reliably trigger the bug.
It isn't a bug, but the expected and intentional behavior.
next prev parent reply other threads:[~2023-03-23 20:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 19:16 bug#62355: 30.0.50; C-g doesn't always quit minibuffer on first press Toon claes
2023-03-22 3:29 ` Eli Zaretskii
2023-03-23 19:31 ` Sean Whitton
2023-03-23 19:47 ` Drew Adams
2023-03-23 20:09 ` Eli Zaretskii [this message]
2023-03-24 0:01 ` Sean Whitton
2023-03-24 6:12 ` Eli Zaretskii
2023-03-24 7:56 ` Toon Claes
2023-03-24 11:56 ` Eli Zaretskii
2023-03-24 15:32 ` Toon Claes
2023-03-24 18:32 ` Eli Zaretskii
2023-03-24 19:17 ` Sean Whitton
2023-03-24 12:39 ` João Távora
2023-03-26 20:44 ` bug#62468: 30.0.50; Improve Icomplete while-no-input s.t. C-g quits the minibuffer Sean Whitton
2023-03-24 21:59 ` bug#62355: 30.0.50; C-g doesn't always quit minibuffer on first press Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83sfdv44df.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62355@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=spwhitton@spwhitton.name \
--cc=toon@to1.studio \
/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).