#11121: Set up good defaults for sage's mercurial
---------------------------+------------------------------------------------
Reporter: kini | Owner: tbd
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-4.7
Component: packages | Keywords: mercurial, git, diff, patches
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by kini):
Trying out `sage-sdist` I find that making `hg diff` go to a pager by
default might screw up some of the scripts (or at the very least cause
them to become interactive when they shouldn't be). This is bad, but
should I make `hg diff` not go to a pager by default, or just stick a
`--pager=` on any usages of `hg diff` in scripts? Paging diffs is a really
nice feature that I think should be standard, but on the other hand it
seems a bit intrusive to have to explicitly specify `--pager=` in a
script.
Then again, why are we even running `hg diff` in scripts? All the examples
of this I could find were either just standalone lines running `hg diff`,
or, in one case, `local/bin/sage-pkg`, an attempt to figure out whether
uncommitted changes existed in the directory (which could just as easily
be done by searching `$(hg summary)` for "(clean)", if I'm not mistaken.
Any comments?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11121#comment:17>
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.
