From: Wincent Colaiuta <win@wincent.com>
Date: Fri, 02 May 2008 18:40:40 GMT
Subject: Re: To page or not to page
Message-ID: <15C1122F-B6BA-4599-A40C-181D131CD252@wincent.com>
In-Reply-To: <247FB870-E42E-4FFA-B230-8A377748C731@sb.org>

El 2/5/2008, a las 18:56, Kevin Ballard escribió:
> On May 2, 2008, at 12:13 PM, Wincent Colaiuta wrote:
>
>> El 2/5/2008, a las 14:36, Jeff King escribió:
>>> On Fri, May 02, 2008 at 12:34:10PM +0200, Wincent Colaiuta wrote:
>>>
>>>> But evidently given that there has been so much backlash against  
>>>> the
>>>> patch the only way to keep everyone happy will be to make this
>>>> configurable.
>>>
>>> Agreed.
>>>
>>> But I wonder why there seems to be such a split between people who
>>> clearly have short git-status output, and those who have long git- 
>>> status
>>> output.
>>
>> I generally try to work on one thing at a time and keep the status  
>> output short -- and I imagine that that's the way most people work  
>> -- but there are certain things where long output is going to be  
>> unavoidable, like renaming a directory with lots of files in it.  
>> And when that happens, seeing only the bottom of the "git status"  
>> output and not the top is not what I want 100% of the time.
>
> Doesn't your terminal have the ability to scroll? If my git-status  
> output is longer than my terminal's height, I just hit Page Up to  
> see the top.

Of course it does, but page up won't necessarily take me to the top of  
the "git status" output; usually it takes me to somewhere before it or  
somewhere after it.

Wincent