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

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Nov 27, 2009, 09:31 UTC
Message-ID: <alpine.DEB.1.00.0911271027510.4521@intel-tinevez-2-302>
In-Reply-To: <20091127062013.GA20844@coredump.intra.peff.net>

Hi,

On Fri, 27 Nov 2009, Jeff King wrote:

Show 13 quoted lines

> On Thu, Nov 26, 2009 at 10:56:55AM -0700, James Pickens wrote:
> 
> > On Wed, Nov 25, 2009 at 3:20 PM, Jeff King <peff@peff.net> wrote:
> > > Sure, there are all those downsides. But what is the other option? 
> > > Making me use the command line option (or pathspec magic) every 
> > > single time I invoke git grep?
> > 
> > Yes, but only when you want non-default behavior, not every single 
> > time.
> 
> Did you miss the part of the thread where I explained that in certain 
> repos, I want it one way every single time, and in others, I want it the 
> other way?

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 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.

Ciao, Dscho