From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 bc55a57: * lisp/menu-bar.el (kill-this-buffer): Doc fix. (Bug#26466)
Date: Mon, 17 Apr 2017 12:05:02 -0400 [thread overview]
Message-ID: <jwvlgqzxc5o.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83fuh7drut.fsf@gnu.org
> The request for documenting the subtlety was voiced more than once
> over the years,
IOW, people have complained about that buggy behavior.
> and I saw no reason not to act on that.
Agreed. Documenting the bug seems like a poorer choice than fixing it, tho.
> We document similar limitations and subtleties all over the place, so
> there's nothing extraordinary in this case.
The difference is that we know how to fix the bug rather than document it.
> And I see no ugliness here, so if it exists, it must be minor.
The ugliness is that the kill-this-buffer code uses
menu-bar-non-minibuffer-window-p and
menu-bar-menu-frame-live-and-visible-p both of which consult
menu-updating-frame because they are designed to be used in menu
attributes (as in :enable, :active, ...).
This misuse implies undesirable behavior when menu-updating-frame
happens to have a non-nil value when the command gets run (e.g. bug#8184
where the "fix" just made the command do nothing instead of making it do
what it should do).
So this whole problem is due to a mistake in the original code which
used menu-bar-non-minibuffer-window-p instead of window-minibuffer-p,
without realizing the difference.
It's a plain bug. Minor, but a bug nonetheless.
Stefan
next prev parent reply other threads:[~2017-04-17 16:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170412194437.19648.75020@vcs0.savannah.gnu.org>
[not found] ` <20170412194438.934FD22EE8@vcs0.savannah.gnu.org>
2017-04-12 20:27 ` [Emacs-diffs] emacs-25 bc55a57: * lisp/menu-bar.el (kill-this-buffer): Doc fix. (Bug#26466) Stefan Monnier
2017-04-12 22:03 ` Juri Linkov
2017-04-13 6:41 ` Eli Zaretskii
2017-04-13 23:35 ` Juri Linkov
2017-04-14 6:35 ` martin rudalics
2017-04-16 21:15 ` Juri Linkov
2017-04-14 7:27 ` Eli Zaretskii
2017-04-16 13:42 ` Stefan Monnier
2017-04-16 15:21 ` martin rudalics
2017-04-16 19:18 ` Stefan Monnier
2017-04-16 20:37 ` martin rudalics
2017-04-16 16:54 ` Eli Zaretskii
2017-04-16 19:22 ` Stefan Monnier
2017-04-16 20:07 ` Eli Zaretskii
2017-04-17 3:00 ` Stefan Monnier
2017-04-17 5:39 ` Eli Zaretskii
2017-04-17 12:14 ` Stefan Monnier
2017-04-17 14:35 ` Eli Zaretskii
2017-04-17 16:05 ` Stefan Monnier [this message]
2017-04-17 16:52 ` Eli Zaretskii
2017-04-19 12:12 ` Stefan Monnier
2017-04-17 14:25 ` Richard Stallman
2017-04-13 18:37 ` Stefan Monnier
2017-04-13 23:30 ` Juri Linkov
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=jwvlgqzxc5o.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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).