From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: alan@idiocy.org, rpluim@gmail.com, omari@smileystation.com,
32864@debbugs.gnu.org, artemiog@mac.com,
simon@simonscientific.com
Subject: bug#32864: 26.1; menus don't work correctly in Mac OS Mojave
Date: Mon, 03 Jun 2019 21:20:37 +0300 [thread overview]
Message-ID: <83ftoqttsa.fsf@gnu.org> (raw)
In-Reply-To: <D0EB3A93-A4C2-400B-A01B-8A240AA1ABF7@acm.org> (message from Mattias Engdegård on Mon, 3 Jun 2019 19:25:27 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Mon, 3 Jun 2019 19:25:27 +0200
> Cc: alan@idiocy.org, omari@smileystation.com, artemiog@mac.com,
> Robert Pluim <rpluim@gmail.com>, simon@simonscientific.com
>
> Could someone explain why, exactly, elisp code cannot be run inside
> the event loop?
Because it's a different thread from the main one, where we run Lisp?
(I know nothing about macOS, so apologies if this makes no sense.)
next prev parent reply other threads:[~2019-06-03 18:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 17:40 bug#32864: 26.1; menus don't work correctly in Mac OS Mojave Artemio González López
2018-09-28 19:40 ` Alan Third
[not found] ` <831B596E-F525-41BF-913D-4A976BABBBB0@mac.com>
2018-09-28 19:49 ` Alan Third
2018-10-01 13:12 ` Artemio González López
2018-10-04 18:35 ` Alan Third
2018-11-17 17:15 ` bug#32864: Run from Terminal Omari Norman
2018-11-17 17:19 ` Omari Norman
2019-02-08 8:15 ` bug#32864: 26.1; menus don't work correctly in Mac OS Mojave simonjgeorge
2019-02-11 22:21 ` Alan Third
2019-02-12 10:00 ` Robert Pluim
2019-05-28 18:31 ` Mattias Engdegård
2019-06-03 17:25 ` Mattias Engdegård
2019-06-03 18:20 ` Eli Zaretskii [this message]
2019-06-03 18:52 ` Mattias Engdegård
2019-06-04 16:44 ` Alan Third
2019-06-04 16:53 ` npostavs
2019-06-04 21:08 ` Mattias Engdegård
2019-06-05 21:27 ` Alan Third
2019-06-20 5:44 ` Tak Kunihiro
2020-01-10 12:01 ` pierrea
2020-05-01 16:30 ` bug#32864: menus don't work in Mac OS: see similar issue 24472 and workaround there Marc Herbert
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=83ftoqttsa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32864@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=artemiog@mac.com \
--cc=mattiase@acm.org \
--cc=omari@smileystation.com \
--cc=rpluim@gmail.com \
--cc=simon@simonscientific.com \
/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).