Re: [PATCH] grep: --full-tree

From: Jeff King <peff@peff.net>
Date: Nov 27, 2009, 09:59 UTC
Message-ID: <20091127095914.GA4865@sigill.intra.peff.net>
In-Reply-To: <alpine.DEB.1.00.0911271027510.4521@intel-tinevez-2-302>

On Fri, Nov 27, 2009 at 10:31:30AM +0100, Johannes Schindelin wrote:

Show 7 quoted lines

> Guess what.  I have a similar problem, only it is that my "git status" 
> output is _always_ too long, so I always have to page it.
> 
> Once upon a time, Junio applied a patch that implied -p with status.  I 
> was overjoyed.  He reverted that patch later.  Yes, exactly.
> 
> So I end up doing "git config --global ps '-p status'" on every new

If only somebody had written a "pager.status" configuration variable, you could use that. Oh wait. I did. And it shipped in v1.6.0.

Show 7 quoted lines

> account (I usually even forget to curse!), and I really cannot see why you 
> do not do the equivalent "git config fullgrep grep --full-tree" in your 
> repositories (or even the global thing).
>
> The further benefit is that we stop talking about breaking backwards 
> compatibility, and we stop talking about making it hard for Git experts to 
> help newbies.

I guess you missed the part of the thread where I already discussed this. It was here:

  http://article.gmane.org/gmane.comp.version-control.git/133672

-Peff