3,356 reputation
815
bio website phys.psu.edu/~collins
location
age
visits member for 3 years
seen 18 hours ago

Author of latexmk


Oct
13
answered latexmk and \graphicspath
Oct
13
answered latexmk -outdir with \include
Oct
11
awarded  Yearling
Sep
24
awarded  Autobiographer
Jul
2
answered Sublime Text LatexTools fail
Apr
2
comment latexmk with xelatex xdv mode
@davidsedai: I've added some comments.
Apr
2
revised latexmk with xelatex xdv mode
added 604 characters in body
Apr
2
answered latexmk with xelatex xdv mode
Apr
2
comment latexmk with xelatex xdv mode
Could you quantify the improvement in execution time from making an xdv file instead of a pdf file.
Mar
4
revised Generate .1 files from MetaUML .mp files automatically with latexmk
Reference to comment replaced by actual code, to make answer self-contained. (I couldn't do that in my comment.)
Mar
3
comment Generate .1 files from MetaUML .mp files automatically with latexmk
There's actually a bug in the latexmk documentation in the file mpost_latexmkrc. I've put a corrected version at mpost_latexmkrc. It'll appear in the next release of latexmk.
Feb
14
comment Configure latexmk to recognize an old file with a new name
The output files still contain names of generated files. Removing the defaultfilename line simply changes the name of the generated files.
Feb
13
comment Configure latexmk to recognize an old file with a new name
The .asy files contain their base names (e.g., foo-2). So if one of the images is removed, not only do the names of later .asy files also change, but also their contents. The .tex and .pre files produced by the asy program also contain changed file names. So there's no realistic alternative to rerunning the asy program, which is what latexmk does. IMHO, it would be useful to request an update to the asymptote package so that the base string for the produced files can be specified by the user as an optional argument to the asy environment.
Nov
8
comment Latexmk and graphicspath
To diagnose this, we are probably going to need to see a MWE, an exact statement of what you did in each case, and the output from running latexmk.
Nov
8
comment Latexmk and fontspec
To diagnose what happened with the previous command line, you should look very carefully at the resulting output from latexmk. It should say exactly what command line was used, and so you should see whether, for example, xelatex was actually invoked. But the new command line (with the -xelatex and -synctex=1 options) is usually a better way to go.
Nov
8
answered Configuring latexmk to use a preprocessor (lhs2TeX)
Nov
7
answered How to clean auxiliary files within subdirectories with latexmk
Oct
24
revised How to compile a document with the pstool package using the pdflatexmk script?
Add another solution with the making of the pdf delegated to latexmk
Oct
23
comment How to compile a document with the pstool package using the pdflatexmk script?
A suitable place to put the line is in a file named latexmkrc in the same directory as the latex file. That's a configuration file read by latexmk when it starts up. (See the latexmk documentation for more details on how it is configured.)
Oct
21
revised How to compile a document with the pstool package using the pdflatexmk script?
added 270 characters in body