Pager in core should be enabled by default

[Gregory Szorc]

On Wed, Nov 25, 2015 at 9:05 AM, Bryan O'Sullivan <bos at serpentine.com>
wrote:

> On Tue, Nov 24, 2015 at 11:19 PM, Pierre-Yves David <
> pierre-yves.david at ens-lyon.org> wrote:
>
>>
>> I'm definitely not fan of having pager on by default. I like my command
>> line to be a series of commands with predictable behavior and backlog.
>>
>
> So turn it off for yourself, that's what configuration is for – the
> default should follow the most commonly useful case. You already know
> perfectly well that everyone else at the major users of Mercurial has the
> pager enabled, and that git has had the pager turned on by default for
> years. This is a case of playing catch-up with the established norm.
>

I agree with Bryan here. Most users want these things to "just work."
Having `hg log` spew dozens of pages at them, overwhelming their eyeballs,
and causing them to get confused as to how to stop the madness is not a
very helpful default.

If there are bugs in pager, we can all remove local pager settings, test
out the default configuration, and fix as many bugs as possible before 3.7
to ensure we're shipping a reasonable default experience.


>
>
>> But, before diving too much into that the pro/cons pager discussion, I
>> would like to point that this is probably a Sprint-Worthy discussion where
>> people could have a face to face discussion about that and come to a final
>> conclusion instead of using the traditional open-source mailing list way of
>> people getting frustrated at each other by email.
>
>
> I am not happy with the idea of stonewalling what should be a
> straightforward discussion for 4 months.
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> https://selenic.com/mailman/listinfo/mercurial-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20151125/3ddba556/attachment.html>