Add option for sagetex #13
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
sage
aims to be an alternative to commercial programs such as Maple, Matlab, and Mathematica.sagetex
is a package to include sage commands/expressions in TeX documents and doing calculations/plotting thereby.Using
sagetex
requires runtex -> sage -> tex
. As this workflow is pretty similar to the one of biber/makeglossaries, we can implement it quite the same way. So this just checks ifsage
should be run (file with ext =sage
found infilelist
has changed) and if so, runsage
.To be discussed:
cluttex.lua
formakeglossaries
andbiber
you always touch the supposed output file. I'm not quite sure why you do this, so I just didn't copy this. Maybe you can explain why you're doing this and maybe we should do this for sagetex as well.So again @minoki, what are your thoughts on this? (made this a draft again to first discuss these points)