GNU bug report logs - #44333
27.1; macOS menu bar 2-clicks

Previous Next

Package: emacs;

Reported by: Viktor Kharitonovich <viktor.kharitonovich <at> gmail.com>

Date: Fri, 30 Oct 2020 17:58:02 UTC

Severity: normal

Merged with 24719, 32864, 34213

Found in versions 26.0.50, 26.1, 27.0.50, 27.1

Done: Alan Third <alan <at> idiocy.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Alan Third <alan <at> idiocy.org>
To: Mattias EngdegÄrd <mattiase <at> acm.org>
Cc: 44333 <at> debbugs.gnu.org, Viktor Kharitonovich <viktor.kharitonovich <at> gmail.com>
Subject: bug#44333: 27.1; macOS menu bar 2-clicks
Date: Sun, 1 Nov 2020 17:28:43 +0000
On Sun, Nov 01, 2020 at 11:50:32AM +0100, Mattias EngdegÄrd wrote:
> > If anyone else has a simpler solution I'd love to hear it.
> 
> Maybe we are overthinking it. I don't think the Cocoa event loop
> really is running in a different thread. Anecdotal evidence
> (printf!) indicates that it isn't.

On the Mac port? It certainly isn't on the NS port... I don't think
the Mac port even really uses the Cocoa event loop, although I could
easily be wrong.

> (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32864#38 has a
> previous investigation into the matter.)
> 
> I just did the simplest thing possible and it works (with a slight
> latency at times, but perhaps tolerable). I'd like to know what's
> wrong with running Lisp in the event loop. It does appear safe to
> me.

We used to have a *lot* of crashes that were related to the event loop
and lisp and so on, but if you're confident it isn't a problem feel
free to propose a patch and we can give it a go on master.

-- 
Alan Third




This bug report was last modified 4 years and 145 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.