From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric M. Ludlam" Newsgroups: gmane.emacs.devel Subject: Re[2]: IDE features: M-x find-grep Date: Sat, 3 May 2008 22:37:55 -0400 Message-ID: <200805040237.m442btFr016801@projectile.siege-engine.com> References: <200804272236.28969.davi@leals.com> <87skx7gea3.fsf@kfs-lx.rd.rdm> <87k5icp98o.fsf@jurta.org> <481BB15A.9080204@gmail.com> <878wyrat3s.fsf@jurta.org> <200805040116.m441GZNT016282@projectile.siege-engine.com> <481D19D6.9090206@gmail.com> NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1209868719 9385 80.91.229.12 (4 May 2008 02:38:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 May 2008 02:38:39 +0000 (UTC) Cc: juri@jurta.org, storm@cua.dk, davi@leals.com, rms@gnu.org, emacs-devel@gnu.org To: "Lennart Borgman (gmail)" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 04 04:39:12 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JsU87-0007Rs-Uf for ged-emacs-devel@m.gmane.org; Sun, 04 May 2008 04:39:12 +0200 Original-Received: from localhost ([127.0.0.1]:46861 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsU7Q-0005Ez-GW for ged-emacs-devel@m.gmane.org; Sat, 03 May 2008 22:38:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JsU7C-00051F-Md for emacs-devel@gnu.org; Sat, 03 May 2008 22:38:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JsU7A-0004zI-Tq for emacs-devel@gnu.org; Sat, 03 May 2008 22:38:14 -0400 Original-Received: from [199.232.76.173] (port=33886 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsU7A-0004zD-Rc for emacs-devel@gnu.org; Sat, 03 May 2008 22:38:12 -0400 Original-Received: from static-71-184-83-10.bstnma.fios.verizon.net ([71.184.83.10] helo=projectile.siege-engine.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JsU77-0002Ug-Be; Sat, 03 May 2008 22:38:09 -0400 Original-Received: from projectile.siege-engine.com (localhost.localdomain [127.0.0.1]) by projectile.siege-engine.com (8.12.8/8.12.8) with ESMTP id m442buZi016805; Sat, 3 May 2008 22:37:56 -0400 Original-Received: (from zappo@localhost) by projectile.siege-engine.com (8.12.8/8.12.8/Submit) id m442btFr016801; Sat, 3 May 2008 22:37:55 -0400 In-reply-to: <481D19D6.9090206@gmail.com> (lennart.borgman@gmail.com) X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:96412 Archived-At: >>> "Lennart Borgman (gmail)" seems to think that: > > >Eric M. Ludlam wrote: >>>>> Juri Linkov 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. > >One drawback of this might be that it is harder to learn which commands >there are. Maybe this can be cured by showing the command to carry out >on that page. Indeed. You would have half a screen to provide as much information as needed, such as: -------------- Find: Enter string to search for: [-!- ] <- gray widget here [ occur ] - Search this buffer [more] [ multi-occur ] - Search many buffers [more] Arguments and Files for Search: [-!- ] <- gray widget here too [ grep ] - use grep to search files [more] [ lgrep ] - use grep to search for regexp [more] [ find-grep ] - Search files specified by find [more] ----------------- Not that I've used all these functions. Eric -- Eric Ludlam: eric@siege-engine.com Siege: www.siege-engine.com Emacs: http://cedet.sourceforge.net