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

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Nov 27, 2009, 10:53 UTC
Message-ID: <alpine.DEB.1.00.0911271144230.4521@intel-tinevez-2-302>
In-Reply-To: <20091127095914.GA4865@sigill.intra.peff.net>

Hi,

On Fri, 27 Nov 2009, Jeff King wrote:

Show 12 quoted lines

> On Fri, Nov 27, 2009 at 10:31:30AM +0100, Johannes Schindelin wrote:
> 
> > 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.

And it makes things inconsistent. That is why I do not use it. Do you work on 10 different computers? I do. And nothing is more unnerving than the same command producing something different on the different computers.

Sure, after a few minutes of fiddling I find out that it was my fault to begin with, but dammit! if the tool makes it that hard already for an expert, it is outright unusable for new users.

I, for one, do not like Git's reputation, but I am tired of trying to fight for the users. BTW quick question: how many Git _users_ were at the GitTogether at MV? 0?

Show 12 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

I only skimmed it, yes. And I did not plan to participate in this thread. But it seems that my views are not represented enough, even if gitzilla chimed in with the very valid, under-acknowledged and over-ignored message: consistency is good. Corollary: inconsistency is bad.

Ciao, Dscho