#10190: developer's guide: warnings & notes about commit message, cloning and
setting the text editor
-------------------------------+--------------------------------------------
Reporter: mvngu | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: documentation | Keywords: Mercurial, developer's guide
Author: Minh Van Nguyen | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Comment(by kcrisman):
Replying to [comment:9 leif]:
> Perhaps a bit OT: Is there any advantage (perhaps to a new user) of
using Mercurial from the Sage prompt?
>
Yes. Again, this comment can only come from someone who has used command
line stuff for so long that it is second nature (that's not an insult,
just a fact - please take no offense).
"Just" setting up an alias to Sage's HG is already non-intuitive, esp. if
one doesn't know what a .bashrc or whatever is, and then there is the
issue of when one upgrades/builds a new Sage, having to change the
alias... or not setting up an alias, which is what I do in the rare
instances that I need the full Sage HG.
But pointing out for those who have done so before or are comfortable with
such things "here's how easy it is to set this up right" would be fine.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10190#comment:13>
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.
