#7549: Reference manual: class hierarchy, inherited members, underscore
variables
-----------------------------+----------------------------------------------
Reporter: mpatel | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: minor | Milestone:
Component: documentation | Keywords:
Author: Mitesh Patel | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by jhpalmieri):
Replying to [comment:23 mpatel]:
> Replying to [comment:20 jhpalmieri]:
>
> > I noticed that after I built with "-j -iu", edited a few files and ran
"sage -b", then when I built the manual again with "-j -iu", in the
"reading sources" portion of the build, it only processes the changed
files, but in the "writing output" phase, it rewrites all of the files.
This could be a little annoying; can it be avoided?
>
> I've also seen this behavior, but I've been unable reproduce it with
certainty --- at least, with a version of #6187's
[http://trac.sagemath.org/sage_trac/attachment/ticket/6187/trac_6187_testreference.patch
'"testreference" patch']. Are there particular types of changes that
usually trigger the problem?
I'm not sure, but I just saw this message at the beginning of a docbuild:
{{{
WARNING: unsupported build info format in
'/Applications/sage/devel/sage/doc/output/html/en/reference/.buildinfo',
building all
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7549#comment:25>
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.
