Hi David,
> > Sage documentation still has a lot of dangling links. To check if there are
> > some please use the recently added option --warn-links as in:
> >
> > sage --docbuild --warn-links reference html
> >
> > Beware that it triggers a full recompilation of the doc the first time you
> > add
> > the option.
> >
> I tried to use this, but ran into the following stupid glitch. If you do,
> in a clean copy of Sage, the following commands:
>
> sage -b main
> sage --docbuild --warn-links reference html
> sage -clone foo
> sage --docbuild --warn-links reference html
>
> then *every one* of the last three commands will trigger a full rebuild of
> the reference manual (taking several tens of minutes)! This makes it
> basically impossible to use this new command together with Mercurial
> branches, and in particular kills any possibility of getting it to work
> with the patchbot.
I think I found a way to hack into Sphinx configuration so that changing
warn-links do not trigger the full recompilation of the doc. You have to
trigger in by hand if you want. For example in:
sage --docbuild reference html
sage --docbuild --warn-links reference html
The second compilation does nothing. And in
sage --docbuild reference html
touch <some sage source files>
sage --docbuild --warn-links reference html
The second recompilation only warns for the touched files. Is this what we
want ? Or do we want an extra option doing whatever ?
See #12869
Cheers,
Florent
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
