Re: about c8af1de9 (git status uses pager)
- From
Wincent Colaiuta <win@wincent.com>
- Date
- Jul 3, 2008, 20:10 UTC
- Message-ID
- <E80011CA-A8D7-4019-8CE4-CDA226A75608@wincent.com>
- In-Reply-To
- <20080703190829.GA18205@sigill.intra.peff.net>
El 3/7/2008, a las 21:08, Jeff King escribió:
Show 24 quoted lines
> On Thu, Jul 03, 2008 at 03:37:30PM +0200, Wincent Colaiuta wrote: > >>>> This [changing git status to use the pager automatically] was >>>> quite a >>>> nasty change to sneak on people I think. >>> >>> Well, I think that a command producing pages and pages of output >>> without stopping is useless. Therefore, _I_ maintain that it makes >>> tons of sense. >> >> Ditto. For me, the change was very welcome. Sure, usually the status >> output is short, but on those occasions where it isn't (big file >> reorganizations etc) I was quite sick of doing the "git status, oops >> that output was too long let's try again, git -p status" dance. It >> was >> also incongruous with my very first experiences with Git, where I had >> been pleasantly surprised that "git log" automatically invoked the >> pager whereas "svn log" just spewed output into my console until ^C. > > I think there is not much point in discussing whether "git status" > should use a pager. It is obvious at this point that some people love > it, and some people despise it, and it seems to be a matter of > personal > preference. The only sane way forward seems to be configurable paging.
I completely agree. I just don't like it when people use words like "nasty" and "sneak" to describe a change that was discussed in one short and one long thread prior to being incorporated. But you're right; there's no sense in discussing the "whether" any more.
Cheers, Wincent