unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Anders Rydvall <anders@rydvall.com>
Cc: 37007@debbugs.gnu.org
Subject: bug#37007: Problem with the menu-bars in mode "org" and "auctex"
Date: Fri, 23 Aug 2019 09:45:54 +0200	[thread overview]
Message-ID: <5022ad25-75b9-1c41-c20e-ec49531f0514@gmx.at> (raw)
In-Reply-To: <acc42139-e9fb-df8b-90ac-29bb08586d54@rydvall.com>

 > "messages" doesn't capture anything related to the menus as far as I
 > can see. Attached screenshot is after shifting between buffers
 > several times and invoking menus with F10. And different buffers
 > have opened with corrupted menu items and the black bars which at
 > every occasion is corrected with F10. Apparently F10 does something
 > different to the menus than the mouse.

It should mean that we do not update the menu bar at some decisive
moments.  Try evaluating the following noisy form with emacs -Q.

(add-hook 'menu-bar-update-hook (lambda () (ding) (message "%s..%s" (current-buffer) major-mode)))

Here I hear a "ding" and see a message whenever I split a window or
show another buffer in some window.  And I hear the ding when hitting
F10 or clicking on a menu bar item with the mouse.  Do you see any
"anomalies" when doing that?  I mean, does the message intuitively
show the "right" current buffer and its major mode when you randomly
execute some of the actions above?

Sorry, I have no better idea than applying such silly heuristics.

Thanks, martin





  reply	other threads:[~2019-08-23  7:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 14:31 bug#37007: Problem with the menu-bars in mode "org" and "auctex" Anders Rydvall
2019-08-12  8:59 ` martin rudalics
     [not found]   ` <812b33b4-5a21-302b-9791-a3c00f21c7b7@rydvall.com>
     [not found]     ` <6667a28d-c2f4-0476-62ba-9fda510bf32b@gmx.at>
     [not found]       ` <b77b67a5-6ee6-1762-ee15-5ea5510353b4@rydvall.com>
2019-08-14  9:19         ` martin rudalics
2019-08-14 11:34           ` Anders Rydvall
2019-08-15  8:12             ` martin rudalics
     [not found]               ` <f9604ae8-d702-db7d-ea80-321cb6e6c681@rydvall.com>
2019-08-17  8:24                 ` martin rudalics
2019-08-19 11:38                   ` Anders Rydvall
2019-08-21  7:37                     ` martin rudalics
2019-08-21 11:08                       ` Anders Rydvall
2019-08-22  8:07                         ` martin rudalics
2019-08-22 12:00                           ` Anders Rydvall
2019-08-23  7:45                             ` martin rudalics [this message]
2022-04-30 16:59 ` Lars Ingebrigtsen
2022-05-29 13:19   ` 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=5022ad25-75b9-1c41-c20e-ec49531f0514@gmx.at \
    --to=rudalics@gmx.at \
    --cc=37007@debbugs.gnu.org \
    --cc=anders@rydvall.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).