From: Chong Yidong <cyd@stupidchicken.com>
To: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Add lgrep/rgrep commands to Edit > Search submenu
Date: Sun, 25 Jan 2009 13:30:18 -0500 [thread overview]
Message-ID: <87skn7w85h.fsf@cyd.mit.edu> (raw)
In-Reply-To: <87y6x0ph4x.fsf@kfs-lx.rd.rdm> (Kim F. Storm's message of "Sat, 24 Jan 2009 21:45:50 +0100")
storm@cua.dk (Kim F. Storm) writes:
> IMO, lgrep and rgrep are much better suited as menu commands,
> and they would logically fit very well on
> Edit > Search > Search Files...
> Edit > Search > Search Files Recurse...
>
> We may remove the standard grep from Tools - or keep it as
> a more advanced/low-level interface.
Conceptually, the grep commands are not a good fit for the Edit menu.
The Edit menu contains commands that act on the current buffer; the
Tools menu contains commands that do fancier stuff like operating on
multiple files. So, even though Isearch and Grep are both "search
commands", I don't think it's good to consolidate them on the menu bar.
next prev parent reply other threads:[~2009-01-25 18:30 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 [this message]
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
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
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=87skn7w85h.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.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 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).