unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>, "'Dan Nicolaescu'" <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org, "'Kim F. Storm'" <storm@cua.dk>,
	'Gilaras Drakeson' <gilaras@gmail.com>
Subject: RE: Add lgrep/rgrep commands to Edit > Search submenu
Date: Mon, 26 Jan 2009 16:48:16 -0800	[thread overview]
Message-ID: <000f01c98018$f1d8fdb0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <87ab9dll12.fsf@jurta.org>

> I agree, we should keep more key prefixes for other useful things.
> So we can use only one prefix `M-g r' for all grep commands:
> 
> M-g r e         grep
> M-g r l         lgrep
> M-g r r         rgrep
> M-g r f         grep-find
> 
> M-g M-r M-e     grep
> M-g M-r M-l     lgrep
> M-g M-r M-r     rgrep
> M-g M-r M-f     grep-find
> 
> All these key sequences are easy to type.

I don't really care one way or the other, but my reaction is this:

What's wrong with `M-x grep' and so on? Seems easier to remember and nearly as
easy to type. Especially with TAB completion: `M-x lg TAB' (4 chars) vs `M-g r
l' (3 chars). Is the keystroke savings really worth it?

On the other hand (as I've suggested before), it makes sense to have a binding
such as `g' in the *grep* buffer that calls up the last `grep' etc. command
again. Currently, `g' runs `recompile' in *grep*. (Or you could have bindings
`g', `l', `r', and `f' for the various grep flavors, and remember the previous
command of each grep flavor.)

Ignore this, if you feel strongly about it.





  reply	other threads:[~2009-01-27  0:48 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
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 [this message]
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='000f01c98018$f1d8fdb0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=gilaras@gmail.com \
    --cc=juri@jurta.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).