#12058: Mercurial should not enable pager by default
------------------------+---------------------------------------------------
Reporter: jdemeyer | Owner: tbd
Type: defect | Status: needs_info
Priority: blocker | Milestone: sage-4.8
Component: packages | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
------------------------+---------------------------------------------------
Comment(by kini):
Replying to [comment:7 vbraun]:
> If you call mercurial from within sage ('hg-sage' and friends) to diff
then we pass `--config pager.pager=...` in `sage/misc/hg.py`. So whether
or not the pager is enabled by default in the `hgrc` is just a matter of
taste.
The point is that `--config pager.pager=...` won't work unless the pager
extension is enabled. As far as I can tell there is no way to enable an
extension on the fly from a command line call to Mercurial, which makes
sense since extensions can have a rather deep effect on Mercurial's
operation. In the `hgrc`, no pager program is ''defined'', which is a
different matter (and is already what I think we all agree is better than
defining a pager program there).
> My vote would be:
> * Use `HGPLAIN` in scripts if necessary.
> * Keep the pager extension to intentionally break scripts that forget
to set `HGPLAIN`.
Sounds great to me. Keep in mind that the pager extension will not break
scripts that forget to set `$HGPLAIN` unless `$PAGER` is also set while
the script is run, or `pager.pager` is set to something in some `hgrc`
somewhere.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12058#comment:8>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
