From: Robert Pluim <rpluim@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: 32864@debbugs.gnu.org, simonjgeorge <simon@simonscientific.com>
Subject: bug#32864: 26.1; menus don't work correctly in Mac OS Mojave
Date: Tue, 12 Feb 2019 11:00:19 +0100 [thread overview]
Message-ID: <m25ztpe37w.fsf@gmail.com> (raw)
In-Reply-To: <20190211222128.GA24425@breton.holly.idiocy.org> (Alan Third's message of "Mon, 11 Feb 2019 22:21:28 +0000")
Alan Third <alan@idiocy.org> writes:
> On Fri, Feb 08, 2019 at 01:15:35AM -0700, simonjgeorge wrote:
>> Interestingly this bug disappears when you enable Emacs in Accessibility
>> under Security and Privacy in System Preferences.
>
> That’s interesting. I wonder if Emacs is using some accessibility API
> to do its menu opening deferral.
This is emacs-26.1 built on 10.10, but running on 10.14, right? I
donʼt see such problems with my built on 10.14 26.1 (and I donʼt have
Emacs in the Accessibility settings).
Robert
next prev parent reply other threads:[~2019-02-12 10:00 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 [this message]
2019-05-28 18:31 ` Mattias Engdegård
2019-06-03 17:25 ` Mattias Engdegård
2019-06-03 18:20 ` Eli Zaretskii
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=m25ztpe37w.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=32864@debbugs.gnu.org \
--cc=alan@idiocy.org \
--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).