Re: [PATCH] grep: --full-tree
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Nov 27, 2009, 10:37 UTC
- Message-ID
- <vpq8wdsqmm4.fsf@bauges.imag.fr>
- In-Reply-To
- <alpine.DEB.1.00.0911271027510.4521@intel-tinevez-2-302>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 5 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.
In this particular example, a config variable was added (pager.status = true). But one big difference is that while pager.status = true can be /annoying/ for some users, it can never really harm (since the pager will automatically disable itself in the cases where you'd really don't want it).
OTOH, a config variable that actually changes the beahvior of the command can indeed harm. Those who ever tried doing portable programming in PHP, where the apache config can actually change the semantics of the language probably understand what I mean ;-).
> 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).
(I guess you meant alias.fullgrep)
Maybe "mygrep" or "dwimgrep" would be a better name, except for the difficulty to type it: the same alias can be defined to different things on different machines.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/