preprint 0.1

watch

preprint watch will automatically compile your paper if a TeX or graphics source file is changed.

Usage:

preprint [--master MASTER] watch [--exts EXT1, ..., EXTN; --cmd CMD; --diff [SHA]]

Optional arguments:
--master   Name of the root LaTeX file (eg, paper.tex)
--exts     List of file extensions (defaults to `pdf eps tex`)
--cmd      Name of command to run when a change occurs (defaults to `make`)
--diff     Run a latexdiff compile against the given commit SHA from the git repository (HEAD if blank).

For example, to continuously compile the document whenever .tex or figures have changed, and assuming you’ve setup a preprint.json file with the name of your master document, just run:

preprint watch

To continuously run a latexdiff-based compile, showing all changes you’ve made against the HEAD of the git repository, run:

preprint watch --diff

The document will be saved to build/PAPER_NAME_diff.pdf. This is a nice way of keeping track of what you’re doing.

Finally, to continuously run a latediff-based compile against an arbitrary commit in your git history, just copy the commit SHA fragment (say, b91688d) and run:

preprint watch --diff b91688d

diff

preprint diff will typeset the document with revisions highlighted between the currently checked-out version, and a previous git commit. This command is powered by the latexdiff (which is probably installed with your tex distribution). The command also requires latexmk to compile the difference document. This command is compatible with documents that use \input{} to combine text documents; in fact, included documents are inlined recursively. preprint diff was inspired by this blog post by Andy Casey.

Usage:

preprint [--master MASTER] diff PREV_SHA [-n NAME]

Arguments:
PREV_SHA   A SHA fragment or tag name pointing to the previous revision.

Optional arguments:
--master   Name of the root LaTeX file (eg, paper.tex)
-n         Output name of the difference document (eg. diff.tex)

pack

preprint pack prepares a preprint for submission to a journal. This pipeline includes:

1. Creating a build directory and copying over just the required manuscript files,

2. Inlining all inputted latex files,

3. Copying the .bbl bibliography or inlining it into the manuscript, as necessary.

4. Moving figures to the root directory and updating tex source,

5. Deleting comments; don’t be a tweet on @OverheardOnAph,

6. Renaming figures to conform to AASTeX if necessary,

7. todo: Making JPEG versions of figures to to fulfil arXiv file size requirements, if necessary,

This command is inspired by Erik Tollerud’s Astropysics package, but is designed around regular expressions for text transformation. The implementation should thus be easier.

Usage:

preprint [--master MASTER] pack NAME [--style STYLE; --exts EXT1, ..., EXTN]

Arguments:
NAME   Name of the build. Products copied to build/NAME directory.

Optional arguments:
--master   Name of the root LaTeX file (eg, paper.tex)
--exts     File format priority for figures (e.g., ``eps, pdf``)
--style    Style for the build (default is ``aastex``, can also be ``arxiv``).

Note that the --exts option can be used to prefer a certain file format for the build if you maintain both EPS and PDF figure sets. For example, to generate a manuscript for a AAS journal, run:

preprint pack my_aas_build --style aastex --exts eps

And to build for the arxiv, where PDF figures are preferred, run:

preprint pack my_arxiv_build --style arxiv --exts pdf