unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 25113@debbugs.gnu.org
Subject: bug#25113: 25.1.90; Stale menu items after switching to a different major mode (or visiting a buffer)
Date: Mon, 05 Dec 2016 18:27:30 +0200	[thread overview]
Message-ID: <83shq2jq8d.fsf@gnu.org> (raw)
In-Reply-To: <f1a5c5b4-b06e-32d3-313e-fd2c06c4be44@yandex.ru> (message from Dmitry Gutov on Mon, 5 Dec 2016 18:13:36 +0200)

> Cc: 25113@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 5 Dec 2016 18:13:36 +0200
> 
> > When you turn on python-mode or ruby-mode, and click on the
> > problematic menu item ("Ruby" etc.) on the menu bar, do you see
> > x-menu-bar-open-internal called?
> 
> According to 'M-x debug-on-entry', I don't. Should I check that with GDB 
> as well?

Yes, I think so: that function is implemented in C.  Set a breakpoint
in Fx_menu_bar_open_internal.

> > Not reproducible on my system.
> 
> That's too bad. As described menus are pretty broken on my machine. And 
> I'm still on an LTS distribution (Ubuntu 16.04), which must have a lot 
> of users.

Does anyone else using GTK+ build see this?





  reply	other threads:[~2016-12-05 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-04 22:45 bug#25113: 25.1.90; Stale menu items after switching to a different major mode (or visiting a buffer) Dmitry Gutov
2016-12-05 15:41 ` Eli Zaretskii
2016-12-05 16:13   ` Dmitry Gutov
2016-12-05 16:27     ` Eli Zaretskii [this message]
2016-12-05 20:26       ` Dmitry Gutov
2016-12-05 20:58         ` Eli Zaretskii
2016-12-05 21:38       ` Stephen Berman
2016-12-06 14:45         ` Dmitry Gutov
2016-12-06 15:23           ` Ken Brown
2020-08-12  0:25             ` Stefan Kangas
2020-08-12  9:54               ` Dmitry Gutov

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=83shq2jq8d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25113@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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).