You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the latex is compiled inside a temporary directory, latex commands that reference relative files are not resolved. Examples are include and input.
The text was updated successfully, but these errors were encountered:
@dougrich — long delay, but spawn + latex might be a better fit. I believe most of the reason for this module to exist is to avoid gobs of input and output files so that you can go right from a string to pdf data, for example, without feeling like you're hitting the filesystem at all.
Together with gulp-latex, this is getting a few issue reports since it doesn't quite work the way people expect. I think the problem is that node-latex suggests it's a better fit for general latex needs than spawn + pdflatex — which it isn't really unless you want to avoid all the extra stuff latex spits out.
Contemplating a tmp: false flag that would just do work in the cwd and skip cleanup. Would make answering these issues easy, but then it's basically just rewriting spawn + latex.
Since the latex is compiled inside a temporary directory, latex commands that reference relative files are not resolved. Examples are include and input.
The text was updated successfully, but these errors were encountered: