unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Helm <nick@tenpoint.co.nz>
To: 31371@debbugs.gnu.org
Cc: Alan Third <alan@idiocy.org>
Subject: bug#31371: 26.1; Menu-bar stops working after search
Date: Tue, 08 May 2018 17:24:04 +1200	[thread overview]
Message-ID: <m24ljig1or.fsf@tenpoint.co.nz> (raw)
In-Reply-To: <m2lgcwmb9r.fsf@tenpoint.co.nz> (Nick Helm's message of "Mon, 07 May 2018 14:48:16 +1200")

On Mon, 07 May 2018 at 14:48:16 +1200, Nick Helm wrote:

> here's a theory: the problem happens because mainMenu is trying to
> simultaneously be part NSMenu (Help's spotlight search field and the
> context help topics) and part EmacsMenu (Help's standard Lisp menu
> items).

On second glance, I don't think this is quite right, at least it's not
the whole story.

Other apps seem to have a related problem. Open Terminal for example,
click on Help, mouse down and click in the Terminal window, then try to
type a command. It doesn't work, I just get system beeps. TextEdit is
the same.

It's like the Help memu isn't returning focus correctly. Maybe it's a
bug in macOS making this show up?





  reply	other threads:[~2018-05-08  5:24 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
2018-05-07  2:48   ` Nick Helm
2018-05-08  5:24     ` Nick Helm [this message]
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=m24ljig1or.fsf@tenpoint.co.nz \
    --to=nick@tenpoint.co.nz \
    --cc=31371@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    /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).