Re: about c8af1de9 (git status uses pager)
- From
- Tim Stoakes <tim@stoakes.net>
- Date
- Jul 3, 2008, 02:15 UTC
- Message-ID
- <20080703021541.GK18147@mail.rocksoft.com>
- In-Reply-To
- <7vtzfln5zw.fsf@gitster.siamese.dyndns.org>
Junio C Hamano(gitster@pobox.com)@220608-03:01:
Show 14 quoted lines
> Having said all that, I have to say I am regretting to have accepted that > patch to enable pager on status, not because it bothers me personally (it > doesn't primarily because I practically never run git-status because I > consider the command useless and living almost always in Emacs helps), but > because in principle changing anything that existing users are used to is > bad. > > Jeff had a patch to allow boolean configuration variable "pager.<command>" > to override the built-in pager settings during 1.5.6 cycle, and I think it > was a reasonable approach to take. People who want to page output from > git-status can then set "pager.status = true" in their configuration (and > then we can revert c8af1de (make git-status use a pager, 2008-04-23)). > Alternatively we could keep the current status-quo for the default, and > people can say "pager.status = false" in their configuration.
I'd really like to see this. Setting core.pager to `less -FSRX` or similar is not useful for me - I *want* to have -X for eg. `git diff`, but I don't want paging at all for status.
This was quite a nasty change to sneak on people I think.
Tim
-- Tim Stoakes