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.
So the next steps are:
- getting a configurable paging patch that is good enough; I just
posted another trial, but there are still a few caveats. I would
love to hear commentary on whether people find it acceptable.
- once there is a patch, there is still the matter of "on by default,
make people configure off" versus "off by default, make people
configure on". And then you can make arguments about how the default
changes the new user experience, but hopefully there will be a
little less vehemence on both sides, since it is "here's what new
users should see" and not "here's what I am forced to see every
day".
-Peff
--
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
