unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Anthony Michael Agelastos <iqgrande@gmail.com>
Cc: 34213@debbugs.gnu.org
Subject: bug#34213: 27.0.50; Menu bar requires 2 clicks, is unresponsive, or has delays on macOS Mojave
Date: Wed, 30 Jan 2019 19:57:14 +0000	[thread overview]
Message-ID: <20190130195714.GB49662@breton.holly.idiocy.org> (raw)
In-Reply-To: <A8465976-601F-410C-AD3F-206F8238D641@gmail.com>

On Sat, Jan 26, 2019 at 03:14:19PM -0700, Anthony Michael Agelastos wrote:
> 
> I noticed some awkward behavior using Emacs on macOS Mojave. I have
> tried Emacs through MacPorts and Homebrew and have observed this issue
> with all builds. Anyways, when I launch Emacs.app, click on the main
> window, and then click on "Buffers" on the menu bar, it doesn't display.
> Subsequent clicks will typically display it. During normal work, it
> seems as if activating the menu items requires 2 clicks for all of the
> pull-down menus to activate. I also attached a video showing this within
> the original ticket I created for the MacPorts project (see URL below). 
> 
> https://trac.macports.org/ticket/57931

I haven’t got round to looking at this yet. I believe something has
changed in Mojave that affects the way Emacs defers the menu click.

When the menu bar is first populated Emacs only generates the top
level menu bar. When you click on it Emacs then swallows the click and
allows lisp to generate the rest of the menu. Once it’s completed, it
reruns the click.

I think it’s supposed to be an optimisation, but it’s going wrong
somewhere.
-- 
Alan Third





  reply	other threads:[~2019-01-30 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 22:14 bug#34213: 27.0.50; Menu bar requires 2 clicks, is unresponsive, or has delays on macOS Mojave Anthony Michael Agelastos
2019-01-30 19:57 ` Alan Third [this message]
2020-04-06 10:19 ` David Hart
2020-04-06 18:54   ` Alan Third
2020-09-30 15:42     ` Lars Ingebrigtsen

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=20190130195714.GB49662@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=34213@debbugs.gnu.org \
    --cc=iqgrande@gmail.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).