# Tag Info

0

You can use the clip function in asymptote. You give the clip command a path and anything previously drawn outside that path will be clipped away. The size command is not needed here. unitsize(1cm); // size(10cm); draw(unitcircle); draw((-5, 0) -- (5, 0)); draw((0, -5) -- (0, 5)); clip(shift(-0.5,-0.5)*scale(5.5)*unitsquare); draw(shift(3,3)*unitcircle, ...

5

Looks like a job for shell escape (\write18): \documentclass{article} \begin{filecontents*}{\jobname2.tex} \documentclass{article} \usepackage{blindtext} \begin{document} \blindtext[2] \end{document} \end{filecontents*} \usepackage{pdfpages} \immediate\write18{pdflatex \jobname2} \begin{document} \includepdf{\jobname2.pdf} \end{document} I've used the ...

4

Perhaps this is what you want: Use bashful package, which allows the execution of shell commands or external programs (I can test this only on Linux right now) The external program(s)/commands must be 'enclosed' in a \bash ... \END pair. Note: The compilation of the 2nd file is done each time when the outer wrapper document is compiled. tex1.tex ...

1

Tags might come in handy for this use case and luckily there is a LaTeX package (now, v1.0 is from August 2011) called tagging for that. Check out the following mini example. main.tex: \documentclass{article} \usepackage{tagging} \begin{document} \tagged{programmers}{Include programmers section} \tagged{riskanalyst}{Include riskanalyst section} ...

2

Just a quick example with docmute. Please note that I only put some packages in the preambles to emphasize that they must be identical or debugging will be difficult, if even possible. IMPORTANT: To prevent really difficult debugging, make very sure that the individual *.tex file with preambles actually do compile individually before running the main ...

4

Let us say you have this standalone file named plotting.tex \documentclass{standalone} \usepackage{pgfplots} \pgfplotsset{compat=1.12} \begin{document} \begin{tikzpicture} \begin{axis}[ xlabel={$x$}, ylabel={$y$}, ] \addplot[blue] {x^2}; \end{axis} \end{tikzpicture} \end{document} which compiles stand alone and produces a graph. Now let us say this is ...

4

All the file input tests use \input@path as well as the standard TEXINPUTS variable, personally I find it easier to just set TEXINPUTS rather than use \input@path (\graphicspath just sets a version of \input@path used locally during the scope of \includegraphics) However if you want to use the macro directory list for all such operations, replace ...

2

Looking at this pgfplots' feature request, I found this old question. I once stumbled on this problem and found a solution (Unfortunately, I didn't documented where the solution came from, I guess not totally from myself). It's not exactly perfect but works. I define the following macro \makeatletter \def\relativepath{\import@path} \makeatother And use it ...

Top 50 recent answers are included