unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Marc Herbert <marc.herbert@gmail.com>
To: 32864@debbugs.gnu.org
Subject: bug#32864: menus don't work in Mac OS: see similar issue 24472 and workaround there
Date: Fri, 1 May 2020 09:30:26 -0700	[thread overview]
Message-ID: <CA+rkZbhZ6Chy8M6G1WCU--D0nUQs9SC1YQJjPsEgMMAC_iiaGg@mail.gmail.com> (raw)
In-Reply-To: <58D0E98D-F0AC-4167-8D4F-DC6AADBCF12D@mac.com>

> So why does Emacs do this to begin with? Because the menu contents are generated dynamically from elisp code each time.
> ...
> IIRC the Emacs menu is different from the others as it’s not built from elisp, it’s hard‐coded.

See similar issue https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24472
and successful, one-line .emacs workaround there.





      parent reply	other threads:[~2020-05-01 16:30 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
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 ` Marc Herbert [this message]

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=CA+rkZbhZ6Chy8M6G1WCU--D0nUQs9SC1YQJjPsEgMMAC_iiaGg@mail.gmail.com \
    --to=marc.herbert@gmail.com \
    --cc=32864@debbugs.gnu.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).