git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-rebase-interactive: avoid breaking when GREP_OPTIONS="-H"
Date: Tue, 8 Sep 2009 06:47:56 +0000	[thread overview]
Message-ID: <20090908064756.GA14155@sajinet.com.pe> (raw)
In-Reply-To: <7v7hwar1fp.fsf@alter.siamese.dyndns.org>

On Mon, Sep 07, 2009 at 12:37:30PM -0700, Junio C Hamano wrote:
> 
> How does your patch help when the user has GREP_OPTIONS=-C3 in the
> environment?

It wouldn't help but at least wouldn't break aborting with an script
error since you will always get a number.

> I think a saner workaround for this user environment bug (or GNU grep
> misfeature) is to unset GREP_OPTIONS at the beginning of the script, or
> even in git-sh-setup.

agree, and since grep is used almost everywhere filtering in git-sh-setup
like CDPATH is makes sense, with the only user of grep that wouldn't
benefit from that being git-mergetool--lib.sh AFAIK.

will test and submit a fix for that later, but still think the original
patch at least improves the status quo (will protect also when using
custom grep wrappers as reported earlier) and doesn't do any harm as wc
is already a dependency as well and was part of the original code as well.

Carlo

  reply	other threads:[~2009-09-08  6:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 12:56 [PATCH] git-rebase-interactive: avoid breaking when GREP_OPTIONS="-H" Carlo Marcelo Arenas Belon
2009-09-07 13:25 ` Dave Rodgman
2009-09-07 19:37 ` Junio C Hamano
2009-09-08  6:47   ` Carlo Marcelo Arenas Belon [this message]
2009-09-08  6:54     ` Junio C Hamano
2009-09-08  7:02   ` Junio C Hamano
2009-09-08  8:31     ` Carlo Marcelo Arenas Belon

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=20090908064756.GA14155@sajinet.com.pe \
    --to=carenas@sajinet.com.pe \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).