From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 14920@debbugs.gnu.org
Subject: bug#14920: 24.3.50; Move search menu items to Search menu
Date: Fri, 29 Apr 2016 15:09:47 +0200 [thread overview]
Message-ID: <87a8kca7dw.fsf@gnus.org> (raw)
In-Reply-To: <6fc45756-676e-457d-801c-4d8ab14a5bd4@default> (Drew Adams's message of "Sat, 20 Jul 2013 17:37:33 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Menu `Tools' is overloaded and becoming a catch-all - a place to throw
> stuff that one doesn't want to take the time to find a good place for.
>
> Search stuff should all be moved to menu `Search'. This includes, e.g.,
> `Search Files (grep)' and `Directory Search' (not sure of this one,
> since this submenu seems to be a hodgepodge of directory-service
> commands and is not limited to directory-service _search_ - see bug
> #14919).
"Directory Search" has been renamed -- it's not about search.
> I also recommend moving menu `Search' to the top level, out from under
> `Edit', and moving menu `Replace' under `Search' (it would be search and
> replace, but a top-level menu name needs to be short).
Hm... It's odd that "Search" is under edit, perhaps. I mean, you want
to be able to search in non-editing modes, too.
Replace wouldn't be that natural in non-editing modes, but...
> I also recommend moving menus `Bookmarks' and `Go To' under top-level
> menu `Search'.
>
> Menu `Search' might also include submenu `Spell Checking'. If that is
> not moved to `Search' it should be moved to `Edit' from `Tools'.
Hm... not sure...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-29 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 0:37 bug#14920: 24.3.50; Move search menu items to Search menu Drew Adams
2016-04-29 13:09 ` Lars Ingebrigtsen [this message]
2021-05-30 6:49 ` Lars Ingebrigtsen
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=87a8kca7dw.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=14920@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 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).