From: Jeremy Bryant via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71761@debbugs.gnu.org, tpeplt@gmail.com, monnier@iro.umontreal.ca
Subject: bug#71761: 29.3; Emacs-Lisp menu display is incorrect during Edebug
Date: Sat, 29 Jun 2024 23:04:35 +0100 [thread overview]
Message-ID: <87o77jflsc.fsf@jeremybryant.net> (raw)
In-Reply-To: <86r0cfj4pp.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 Jun 2024 15:47:30 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > That could be a bug in TTY menus, or maybe a side effect of how the
>> > menu bar is displayed there.
>>
>> I fear I wasn't clear in my diagnostics.
>>
>> It appears from my testing the bug is in Emacs GUI, and the TTY menus
>> are OK.
>
> I understood that. But are you aware of the fact that TTY menus use
> the same code from xmenu.c that the X build without toolkits uses?
>
> My point is that the fact that TTY menus don't show this problem is
> because there's a bug in xmenu.c which somehow hides this problem.
> After all, when the code which traverses the menu structures finds a
> menu item that already exists, it could start a new pane or it could
> overwrite the existing one. Which one is the buggy one?
Interesting (glad to hear my testing was understood properly.).
I wasn't aware of this, thanks for explaining the code structure.
next prev parent reply other threads:[~2024-06-29 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 20:32 bug#71761: 29.3; Emacs-Lisp menu display is incorrect during Edebug tpeplt
2024-06-28 18:10 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-29 11:05 ` Eli Zaretskii
2024-06-29 12:20 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-29 12:47 ` Eli Zaretskii
2024-06-29 22:04 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-30 4:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o77jflsc.fsf@jeremybryant.net \
--to=bug-gnu-emacs@gnu.org \
--cc=71761@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jb@jeremybryant.net \
--cc=monnier@iro.umontreal.ca \
--cc=tpeplt@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.