Re: To page or not to page
- From
Jeff King <peff@peff.net>
- Date
- May 2, 2008, 05:45 UTC
- Message-ID
- <20080502054508.GA28506@sigill.intra.peff.net>
- In-Reply-To
- <70F76C0E-E16D-4047-873D-7FD19FDBB55D@sb.org>
On Fri, May 02, 2008 at 01:41:05AM -0400, Kevin Ballard wrote:
Show 8 quoted lines
> c8af1de9cfa0a5678ae766777e0f905e60b69fda makes git status use a pager. I > think this is a horrible choice. Now when I type `git status` I have to > type "q" to get back to my shell, and I've lost the output of the pager. > It makes sense for commands with long output like `git log`, but `git > status` rarely has output longer than my terminal's height, and so making > it use the pager simply detracts from its functionality. > > Does anybody have any comments or opinions about this either way?
I agree with you; I don't like it at all. Probably whether or not to use a pager for a given command should be controlled by a "pager.<cmd>" config variable.
In the meantime, try adding FX to your LESS environment variable.
-Peff