From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Chong Yidong' <cyd@stupidchicken.com>,
emacs-devel@gnu.org, "'Kim F. Storm'" <storm@cua.dk>
Subject: Re: Add lgrep/rgrep commands to Edit > Search submenu
Date: Sun, 25 Jan 2009 23:45:03 +0200 [thread overview]
Message-ID: <87mydf9i1s.fsf@jurta.org> (raw)
In-Reply-To: <004301c97f27$9371ca50$0200a8c0@us.oracle.com> (Drew Adams's message of "Sun, 25 Jan 2009 12:00:30 -0800")
> All search stuff should be together, in a Search menu. That includes things like
> grep and occur.
>
> It doesn't matter much whether Search is a submenu of the Edit menu or the Tools
> menu. However, one reason to not put Search under Edit could be that some modes
> might want to remove Edit but keep search stuff.
>
> Personally, I put the Search menu at the top level. And I include as submenus of
> Search things like replace, tags, bookmarks, and goto. Those are all
> search-like, IMO.
I think this is a good idea because currently even "Go To" submenu
contains search commands like "Find Tag", "Tags Apropos".
> FWIW, I also agree with Kim's suggestion (on the bug list) to move Options from
> the top level. I'd sooner see Options under Edit, and Search at the top level.
> Or both under Edit. Or Options under Edit and Search under Tools.
>
> Typical places for setting preferences are under Edit or File. Moving Options
> from the top level to Edit or File would obviate some of the problems (e.g.
> currently, for GNUS, in the bug list) for menu-bar space. And users would still
> have no problem finding Options - they do so for other apps (Options typically
> being called something like Preferences, Settings, or Configure Settings).
What is interesting is that Firefox has the Preferences item
under Edit on GNU/Linux, but under Tools on Windows.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-01-25 21:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 20:45 Add lgrep/rgrep commands to Edit > Search submenu Kim F. Storm
2009-01-24 21:09 ` Dan Nicolaescu
2009-01-25 0:57 ` Juri Linkov
2009-01-25 0:55 ` Juri Linkov
2009-01-25 1:04 ` Lennart Borgman
2009-01-25 18:14 ` Richard M Stallman
2009-01-25 21:30 ` Lennart Borgman
2009-01-25 21:33 ` Juri Linkov
2009-01-25 18:30 ` Chong Yidong
2009-01-25 19:22 ` Kim F. Storm
2009-01-25 21:37 ` Juri Linkov
2009-01-25 22:43 ` Kim F. Storm
2009-01-26 1:54 ` Stefan Monnier
2009-01-25 20:00 ` Drew Adams
2009-01-25 21:45 ` Juri Linkov [this message]
2009-01-26 4:09 ` Eli Zaretskii
2009-01-25 21:33 ` Lennart Borgman
2009-01-25 19:04 ` Gilaras Drakeson
2009-01-25 21:47 ` Juri Linkov
2009-01-25 22:49 ` Kim F. Storm
2009-01-26 0:42 ` Dan Nicolaescu
2009-01-26 23:52 ` Juri Linkov
2009-01-27 0:48 ` Drew Adams
2009-01-27 17:40 ` Kim F. Storm
2009-01-26 23:48 ` Juri Linkov
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=87mydf9i1s.fsf@jurta.org \
--to=juri@jurta.org \
--cc=cyd@stupidchicken.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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.