From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "8116@debbugs.gnu.org" <8116@debbugs.gnu.org>
Subject: bug#8116: [External] : Re: bug#8116: 24.0.50; `minibuffer-message': ignore mouse-up event for `sit-for'?
Date: Sun, 18 Jul 2021 14:10:23 +0000 [thread overview]
Message-ID: <SJ0PR10MB548804503953DDC38AA853D8F3E09@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83pmvg2jzn.fsf@gnu.org>
> > > If you pop up a menu (e.g. using `x-popup-menu') and one of its items
> > > calls `minibuffer-message', the user will never see the message,
> > > presumably because the call to `sit-for' in `minibuffer-message' sees
> > > the mouse-up event (from choosing the menu item) as user input,
> > > canceling the `sit-for' timeout.
> >
> > Do you have a test case that demonstrates the problem?
>
> You won't be able to see this on any system but MS-Windows. On
> Windows, the Emacs menus are implemented in a way that has this
> unfortunate side effect: we basically preempt the Emacs command loop
> for as long as the menu stays open.
>
> If someone wants to redesign how Emacs menus are implemented on
> Windows, I think that would be very welcome. But until that happens,
> this is Emacs "functioning as designed", not some easily-fixed bug.
Thanks for this info. I guess the bug can then either
be closed or kept open in the wishlist, the fix needing
redesign etc.
I wonder if this effect should be mentioned in the manual?
prev parent reply other threads:[~2021-07-18 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 16:50 bug#8116: 24.0.50; `minibuffer-message': ignore mouse-up event for `sit-for'? Drew Adams
2011-02-25 18:06 ` Stefan Monnier
2011-02-25 18:27 ` Drew Adams
2021-07-18 0:30 ` Lars Ingebrigtsen
2021-07-18 2:05 ` bug#8116: [External] : " Drew Adams
2021-07-18 12:04 ` Lars Ingebrigtsen
2021-07-18 14:18 ` Drew Adams
2021-07-18 6:50 ` Eli Zaretskii
2021-07-18 12:09 ` Lars Ingebrigtsen
2021-07-18 14:10 ` Drew Adams [this message]
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=SJ0PR10MB548804503953DDC38AA853D8F3E09@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=8116@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).