From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 bc55a57: * lisp/menu-bar.el (kill-this-buffer): Doc fix. (Bug#26466)
Date: Fri, 14 Apr 2017 02:30:57 +0300 [thread overview]
Message-ID: <87wpan9972.fsf@localhost> (raw)
In-Reply-To: <jwvzifk40li.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Thu, 13 Apr 2017 14:37:03 -0400")
>>> - Why did we decide to use menu-bar-non-minibuffer-window-p rather than
>>> checking something like (window-minibuffer-p (frame-selected-window))?
>> ‘menu-bar-non-minibuffer-window-p’ already does this, and additionally
>> takes into account ‘menu-updating-frame’ and checks for ‘frame-live-p’.
>
> But that's exactly the question: why pay attention to
> menu-updating-frame and frame-live-p?
menu-bar-non-minibuffer-window-p is used to check whether a menu item
should be enabled, so indeed this is not needed in kill-this-buffer
that should work with just (window-minibuffer-p (frame-selected-window)).
But I still believe that exiting the active minibuffer by kill-this-buffer
makes sense only in the context of menu-bar/tool-bar where the same icon
can be shared to do two different things: either exit the minibuffer
or kill the current buffer. I can't imagine why anyone would want to do
this with kill-current-buffer bound to the same key when there is already
the special key C-g and also keyboard-escape-quit to exit the minibuffer.
prev parent reply other threads:[~2017-04-13 23:30 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
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 [this message]
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=87wpan9972.fsf@localhost \
--to=juri@linkov.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).