git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Ratterman <jratt0@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] Add two grep config options
Date: Mon, 28 Mar 2011 13:08:11 -0500	[thread overview]
Message-ID: <AANLkTinNM_tf=rJYXLO8cgaxwpAz2pi8G4nJiwZ9RLR6@mail.gmail.com> (raw)
In-Reply-To: <7vvcz3yxs8.fsf@alter.siamese.dyndns.org>

On Mon, Mar 28, 2011 at 12:12 PM, Junio C Hamano <gitster@pobox.com> wrote:
> But would any user go all that trouble, just not to say "-nE" from the
> command line (or use an alias that was designed not to crash with
> scripts)?
>

I use the $GREP_OPTIONS environment variable to add -n and -P (pcre)
to my grep commands by default.  Coming from a strong Perl background,
I don't know the *exact* difference between basic and extended, so I
do not usually realize I need -E until it gets a little too
complicated.  I generally forget line numbers until I want to start
editing the file, making me run the grep command a second time.  For
me, it is much easier to have them in the environment/config-file,
since I never want to avoid them.

Joe

  parent reply	other threads:[~2011-03-28 18:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 21:21 [PATCH] Add two grep config options Joe Ratterman
2011-03-25 23:25 ` Junio C Hamano
2011-03-28  7:24   ` Michael J Gruber
2011-03-28 11:54     ` Jeff King
2011-03-28 12:00       ` Michael J Gruber
2011-03-28 12:09         ` Jeff King
2011-03-28 17:12       ` Junio C Hamano
2011-03-28 17:21         ` Jeff King
2011-03-28 18:39           ` Junio C Hamano
2011-03-28 18:08         ` Joe Ratterman [this message]
2011-03-28 12:13     ` Bert Wesarg
2011-03-28 14:48       ` Joe Ratterman
2011-03-28 17:14         ` Junio C Hamano
2011-03-28 22:12   ` [PATCH] grep: allow -E and -n to be turned on by default via configuration Junio C Hamano
2011-03-28 22:14     ` Junio C Hamano
2011-03-28 22:41     ` Joe Ratterman
2011-03-28 23:16       ` Junio C Hamano
2011-03-29  3:12     ` Joe Ratterman
2011-03-30 19:31       ` [PATCH v3] " Joe Ratterman

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='AANLkTinNM_tf=rJYXLO8cgaxwpAz2pi8G4nJiwZ9RLR6@mail.gmail.com' \
    --to=jratt0@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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. 
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 NNTP newsgroup(s).