Hi, On Fri, 27 Nov 2009, Matthieu Moy wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > > 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). It changes behavior. And worse: it changes behavior _in a different manner_ in different repositories. I have too many of them to remember what I set where. So it is harmful in a very real sense. > > 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) You guessed right, and likewise alias.ps. Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html