unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Bryant <jb@jeremybryant.net>
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 15:47:30 +0300	[thread overview]
Message-ID: <86r0cfj4pp.fsf@gnu.org> (raw)
In-Reply-To: <87sewwgctq.fsf@jeremybryant.net> (message from Jeremy Bryant on Sat, 29 Jun 2024 13:20:33 +0100)

> From: Jeremy Bryant <jb@jeremybryant.net>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  tpeplt@gmail.com,
>   71761@debbugs.gnu.org
> Date: Sat, 29 Jun 2024 13:20:33 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> >    Please let me know if anything above is unclear or if you are unable
> >> > to reproduce this problem.
> >> 
> >> The following may help to narrow down the problem:
> >> 
> >> In Emacs 29.4:
> >> I am able to reproduce the bug in Emacs GUI
> >> But in Emacs TTY (emacs -nw), the problem seems absent, the menu bar
> >> appears correct.
> >
> > 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?






  reply	other threads:[~2024-06-29 12:47 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 [this message]
2024-06-29 22:04         ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
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

  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=86r0cfj4pp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71761@debbugs.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 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).