From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Juri Linkov <juri@jurta.org>
Cc: lennart.borgman@gmail.com, emacs-devel@gnu.org, davi@leals.com,
rms@gnu.org, storm@cua.dk
Subject: Re[2]: IDE features: M-x find-grep
Date: Sat, 3 May 2008 21:16:35 -0400 [thread overview]
Message-ID: <200805040116.m441GZNT016282@projectile.siege-engine.com> (raw)
In-Reply-To: <878wyrat3s.fsf@jurta.org> (message from Juri Linkov on Sun, 04 May 2008 02:03:03 +0300)
>>> Juri Linkov <juri@jurta.org> seems to think that:
>> Yes, I use to say that they should be in the Edit menu every time we
>> discuss this ... ;-)
>>
>> Seriously, they are very useful and I see no reason not to put them
>> there. And `occur' and `multi-occur' should be there too, of course.
>>
>> There are lots of commands that are "worth putting in the menu" if we
>> judge by their usefulness. But if we put them all in the menu it will
>> be so big it is inconvenient to use. So arguing that "this command is
>> worth including" is not a good way to think about the question.
>
>The menu is not necessarily flat. Using submenus it would be possible
>to organize most useful commands in a convenient way. For instance,
>the "Search" menu could have submenus "Search files" for the grep family
>of commands, and "Search buffers" for the occur family of commands.
A better option is that the menu item might just be "find". Instead
of a singular minibuffer prompt to a specific grep command, a buffer
explaining different grep options could be provided. The cursor lands
on a text widget, and then the users types in the expression, and then
choses the right type of grep/find command from a selection of
buttons. An expert Emacs user would, of course, just type M-x
my-favorite-grep-command RET, but for a new user, this would cover all
the bases in one menu item.
Eric
--
Eric Ludlam: eric@siege-engine.com
Siege: www.siege-engine.com Emacs: http://cedet.sourceforge.net
next prev parent reply other threads:[~2008-05-04 1:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 20:36 IDE features: M-x find-grep Davi Leal
2008-04-27 21:12 ` Phil Jackson
2008-04-27 22:10 ` Davi Leal
2008-04-27 21:48 ` Kim F. Storm
2008-04-27 22:44 ` Davi Leal
2008-05-02 23:46 ` Juri Linkov
2008-05-03 0:27 ` Lennart Borgman (gmail)
2008-05-03 21:01 ` Richard M Stallman
2008-05-03 23:03 ` Juri Linkov
2008-05-04 1:16 ` Eric M. Ludlam [this message]
2008-05-04 2:05 ` Lennart Borgman (gmail)
2008-05-04 2:37 ` Re[2]: " Eric M. Ludlam
2008-05-05 20:21 ` Lennart Borgman (gmail)
2008-05-04 20:07 ` Richard M Stallman
2008-05-04 23:17 ` Juri Linkov
2008-05-04 23:47 ` Drew Adams
2008-05-05 15:14 ` Richard M Stallman
2008-05-05 15:14 ` Richard M Stallman
2008-05-04 2:04 ` Lennart Borgman (gmail)
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=200805040116.m441GZNT016282@projectile.siege-engine.com \
--to=eric@siege-engine.com \
--cc=davi@leals.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=lennart.borgman@gmail.com \
--cc=rms@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).