From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>
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: Fri, 24 Mar 2023 12:17:20 -0700 [thread overview]
Message-ID: <871qleez7j.fsf@athena.silentflame.com> (raw)
In-Reply-To: <83r0teekzm.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 24 Mar 2023 09:12:13 +0300")
Hello,
On Fri 24 Mar 2023 at 09:12AM +03, Eli Zaretskii wrote:
>> Date: Thu, 23 Mar 2023 17:01:08 -0700
>> From: Sean Whitton <spwhitton@spwhitton.name>
>> Cc: toon@to1.studio, 62355@debbugs.gnu.org, joaotavora@gmail.com
>>
>> On Thu, Mar 23, 2023 at 10:09:00PM +0200, Eli Zaretskii wrote:
>> >
>> > It isn't a bug, but the expected and intentional behavior.
>>
>> I thought that the idea with Icomplete &c. was that they would stop what they
>> are doing in response to any keystrokes, not requiring an explicit quit, in
>> order to be maximally unobtrusive.
>
> We may be talking about two different issues.
My apologies for confusing things. I'll file a separate bug.
--
Sean Whitton
next prev parent reply other threads:[~2023-03-24 19:17 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qleez7j.fsf@athena.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=62355@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--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 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.