From: Drew Adams <drew.adams@oracle.com>
To: Drew Adams <drew.adams@oracle.com>,
"52874@debbugs.gnu.org" <52874@debbugs.gnu.org>
Subject: bug#52874: 26.3; Be able to keep current menu-bar menus when minibuffer is used
Date: Wed, 29 Dec 2021 22:22:02 +0000 [thread overview]
Message-ID: <SJ0PR10MB548886D00DF56AE587C73DF7F3449@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR10MB5488AB057F1B1B118F580839F3449@SJ0PR10MB5488.namprd10.prod.outlook.com>
I misstated this. The problem is that when the
minibuffer is active, the menu-bar menus are no
longer those for what was the current buffer
before it was active.
The problem is not the _addition_ of a Minibuf
menu to the menu-bar. The problem is that the
menu-bar menus are changed to be those for the
new current buffer, which is the minibuffer.
It should be enough that menu Minibuf is added,
and so available. There's little sense in
changing the other menus to those for a
relatively plain buffer such as the minibuffer.
Case in point -
In a Dired buffer you have these menus, in
addition to the standard File, Edit, Options,
Buffers, Tools, and Help:
Operate
Mark
Regexp
Immediate
Subdir
Those are lost when the minibuffer is active.
In addition, the "standard" File etc. menus
can have different content depending on the
current mode. Using the mode of the minibuffer
isn't helpful for the menu-bar, in general.
Or at least it sometimes isn't. Hence the
request to _be able_ to keep the menu-bar as
it was before the minibuffer was entered.
next prev parent reply other threads:[~2021-12-29 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 16:37 bug#52874: 26.3; Be able to keep current menu-bar menus when minibuffer is used Drew Adams
2021-12-29 22:22 ` Drew Adams [this message]
2021-12-30 5:57 ` Eli Zaretskii
2021-12-30 15:43 ` bug#52874: [External] : " Drew Adams
2021-12-30 16:42 ` Eli Zaretskii
2021-12-30 17:59 ` Drew Adams
2021-12-30 18:11 ` Eli Zaretskii
2021-12-30 19:05 ` Drew Adams
2021-12-30 20:37 ` Drew Adams
2021-12-31 16:01 ` Drew Adams
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=SJ0PR10MB548886D00DF56AE587C73DF7F3449@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=52874@debbugs.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).