unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Nick Helm <nick@tenpoint.co.nz>
Cc: 31371@debbugs.gnu.org
Subject: bug#31371: 26.1; Menu-bar stops working after search
Date: Sun, 6 May 2018 11:14:11 +0100	[thread overview]
Message-ID: <20180506101411.GA3327@breton.holly.idiocy.org> (raw)
In-Reply-To: <m2a7tep4rm.fsf@tenpoint.co.nz>

On Sun, May 06, 2018 at 02:15:57AM +1200, Nick Helm wrote:
> 
> Emacs menu-bar does not work after a help search on macOS.
> 
>   Emacs -Q
>   Click "Help" in the macOS menu-bar
>   Enter any text in the help search field, e.g. "text"
>   Move the mouse pointer to the right until the help menu disappears
>   Move the mouse pointer back over "Help"
> 
> Note that the Help menu does not reappear and the mouse does not move
> correctly (slows down) while moving over the word "Help". Subsequent
> clicks on the menu-bar do not work as expected either. 

Looks like it goes into some sort of infinite loop calling
ns_update_menubar. If you go to the left so it opens some non‐help
menu, then go back to help it works fine (I think).

The menu code seems pretty horrible to me, so this may take some
time...
-- 
Alan Third





  reply	other threads:[~2018-05-06 10:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 14:15 bug#31371: 26.1; Menu-bar stops working after search Nick Helm
2018-05-06 10:14 ` Alan Third [this message]
2018-05-07  2:48   ` Nick Helm
2018-05-08  5:24     ` Nick Helm
2018-05-08 21:40     ` Alan Third
2018-05-13 10:09       ` Nick Helm
2018-05-18 21:33 ` George Plymale II
2018-05-19  4:26   ` Nick Helm
2019-10-11 11:25 ` Stefan Kangas
2019-10-11 12:04   ` Robert Pluim
2019-10-14  1:50   ` Nick
2019-10-14 12:44     ` Stefan Kangas
2019-10-14 12:55       ` Robert Pluim
2019-10-14 13:14       ` Alan Third
2019-11-05 15:13         ` Stefan Kangas
2019-11-09 10:18           ` Stefan Kangas
2019-11-09 11:29             ` Alan Third
2019-12-31 10:29             ` Stefan Kangas

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=20180506101411.GA3327@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=31371@debbugs.gnu.org \
    --cc=nick@tenpoint.co.nz \
    /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).