all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 52874@debbugs.gnu.org
Subject: bug#52874: [External] : Re: bug#52874: 26.3; Be able to keep current menu-bar menus when minibuffer is used
Date: Thu, 30 Dec 2021 18:42:18 +0200	[thread overview]
Message-ID: <838rw2hwnp.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488B6020B580A347DF02D08F3459@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Thu, 30 Dec 2021 15:43:20 +0000)

> From: Drew Adams <drew.adams@oracle.com>
> CC: "52874@debbugs.gnu.org" <52874@debbugs.gnu.org>
> Date: Thu, 30 Dec 2021 15:43:20 +0000
> 
> > I still don't understand what kind of problem this causes.  In your
> > Dired example, the Dired-specific menu items are not useful in the
> > minibuffer; in fact, using those menu items could get  the user in
> > trouble (recursive minibuffers and all that).
> 
> Please see the original bug report.

I've seen it.

> They _are_ useful for a command that uses the
> minibuffer to browse and use the menu-bar menus.

Then that particular command can add  the menu items it wants back.
There's no need to change how Emacs works because one specific command
wants it to work differently.

> > On the practical side, adding menu items could easily overflow the
> > one screen line allocated to the menu bar, after which the behavior
> > becomes ugly and toolkit-dependent.
> 
> That's a general problem.  It's not particular
> to this context.

You are arguing for a general solution, so I'm pointing out a general
problem with that.

> And the only menu added is Minibuf.

Not in general.  Ever major and minor mode can add something to
the menu bar's top-level menus.

> And if you really think that's a problem then
> the ability to keep the menu-bar as it was when
> the minibuffer is entered could forego adding
> menu Minibuf to the menu-bar.  Not a problem.

There's nothing special with the behavior when you enter the
minibuffer.  It is just a consequence of changing the major mode.





  reply	other threads:[~2021-12-30 16:42 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
2021-12-30  5:57   ` Eli Zaretskii
2021-12-30 15:43     ` bug#52874: [External] : " Drew Adams
2021-12-30 16:42       ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838rw2hwnp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52874@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.