From: Alan Third <alan@idiocy.org>
To: Po Lu <luangruo@yahoo.com>
Cc: "Lars Ingebrigtsen" <larsi@gnus.org>,
52994@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#52994: 29.0.50; Help descriptions from menu bar items don't appear in the echo area
Date: Sat, 22 Jan 2022 11:48:04 +0000 [thread overview]
Message-ID: <Yevu9MvCR8srRckz@idiocy.org> (raw)
In-Reply-To: <87zgnot2rn.fsf@yahoo.com>
On Sat, Jan 22, 2022 at 07:42:52PM +0800, Po Lu wrote:
> Alan Third <alan@idiocy.org> writes:
>
> > It certainly used to be the case that, at least on macOS, opening a
> > menu would freeze Emacs completely, as the menu code would go into its
> > own event loop. Perhaps that's no longer the case.
>
> Hmm? Shouldn't that kind of thing only apply to regular menus (as on X
> with a tookit and GTK), and not the menu bar?
What's the "menu bar" if not the toolkit menus?
--
Alan Third
next prev parent reply other threads:[~2022-01-22 11:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m18rvwwebj.fsf.ref@yahoo.es>
2022-01-04 0:10 ` bug#52994: 29.0.50; Help descriptions from menu bar items don't appear in the echo area Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 8:39 ` Lars Ingebrigtsen
2022-01-15 12:37 ` Alan Third
2022-01-20 10:16 ` Lars Ingebrigtsen
2022-01-20 11:11 ` Alan Third
2022-01-20 11:14 ` Lars Ingebrigtsen
2022-01-20 11:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 11:28 ` Alan Third
2022-01-22 11:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 11:48 ` Alan Third [this message]
2022-01-22 12:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 13:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 13:20 ` Daniel Martín 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=Yevu9MvCR8srRckz@idiocy.org \
--to=alan@idiocy.org \
--cc=52994@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=mardani29@yahoo.es \
/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).