From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>,
56155@debbugs.gnu.org
Subject: bug#56155: 29.0.50; Options menu, toggle menu items not updated
Date: Wed, 29 Jun 2022 01:38:10 +0200 [thread overview]
Message-ID: <m1pmis740t.fsf@yahoo.es> (raw)
In-Reply-To: <CADwFkmkt_eMikOF3=vw-2vKT83ZvcQyLfehczHF5B-U6HGgvCg@mail.gmail.com> (Stefan Kangas's message of "Tue, 28 Jun 2022 14:21:49 -0700")
Stefan Kangas <stefan@marxist.se> writes:
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> What I don't know is if this can only be seen on macOS. On macOS, one can
>> select an option from the menu bar, re-open the Options menu and select another,
>> wihout Emacs running anything in between the two selections that can itself set
>> update_mode_lines. If anything else sets update_mode_lines, the ill effect will
>> not show up. Just clicking in the text area runs a command...
>
> FWIW, I can reproduce the issue consistently on my macOS machine, but
> not on GNU/Linux.
That's interesting. Could you put a breakpoint on that C function on
GNU/Linux to see if it's called, for example, when you close the menu?
That may be the key difference between macOS and the other operating
systems. I don't have a GNU/Linux system at hand right now, but I can
investigate if needed.
(BTW, as an aside, getting a Lisp backtrace using LLDB on macOS is a bit
time-consuming because of all the manual steps to print the pointer
structures. If I have time, I'd like to write an .lldbinit file with
LLDB commands to make this process much simpler, although I don't know
how many people are debugging Emacs using LLDB here.)
next prev parent reply other threads:[~2022-06-28 23:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 9:09 bug#56155: 29.0.50; Options menu, toggle menu items not updated Gerd Möllmann
2022-06-23 10:15 ` Eli Zaretskii
2022-06-28 12:06 ` Gerd Möllmann
2022-06-28 21:21 ` Stefan Kangas
2022-06-28 23:38 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-29 5:32 ` Gerd Möllmann
2022-06-29 6:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-29 8:44 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-29 8:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-29 6:04 ` Gerd Möllmann
2022-06-29 10:16 ` 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=m1pmis740t.fsf@yahoo.es \
--to=bug-gnu-emacs@gnu.org \
--cc=56155@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=mardani29@yahoo.es \
--cc=stefan@marxist.se \
/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).