From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "41862@debbugs.gnu.org" <41862@debbugs.gnu.org>
Subject: bug#41862: [External] : Re: bug#41862: 27.0.91; Isearch menu added to menu-bar
Date: Sun, 13 Jun 2021 14:53:10 +0000 [thread overview]
Message-ID: <SA2PR10MB44749738EB9936E34E2E25A8F3329@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87bl8a582t.fsf@gnus.org>
> > Starting with Emacs 27, `isearch-mode-map'
> > includes`isearch-menu-bar-map', which adds menu
> > `Isearch' to the menu-bar.
>
> Many modes add stuff to the menu bar -- there's nothing
> special about isearch here.
>
> > This should at least be optional, via user option
> > (not requiring a user to fiddle with keymaps).
>
> I don't see why -- the general mechanism we have for
> this works across any mode, so that's more convenient
> than adding some random user options for a mode here
> and there:
>
> (define-key isearch-mode-map [menu-bar] nil)
>
> So I'm closing this bug report.
Just to make sure: Did you read my reply to Juri here?
Like you, I said that there's nothing special about
isearch here.
The point is _not_ to remove/prevent the Isearch menu.
And the point is especially not for any given user
to have to do that, and especially not by fiddling
with keymaps.
The point is for Emacs to find a good solution. I
mentioned the Dired solution, which has long existed,
and which I'm guessing could make sense for Isearch:
When the Isearch menu is shown, consider temporary
removal of another menu (or two) a menu that's not
so useful during Isearch.
That lets you use the Isearch menu without the
annoyance. And yes, whether to do such removal
(and which menu(s) to remove temporarily) could be
user-configurable with an option.
prev parent reply other threads:[~2021-06-13 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 22:05 bug#41862: 27.0.91; Isearch menu added to menu-bar Drew Adams
2020-06-15 22:53 ` Juri Linkov
2020-06-16 1:25 ` Drew Adams
2021-06-13 11:15 ` Lars Ingebrigtsen
2021-06-13 14:53 ` Drew Adams [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SA2PR10MB44749738EB9936E34E2E25A8F3329@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=41862@debbugs.gnu.org \
--cc=larsi@gnus.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 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.