Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Referenced relative files not resolved #11

Open
dougrich opened this issue Dec 6, 2015 · 1 comment
Open

Referenced relative files not resolved #11

dougrich opened this issue Dec 6, 2015 · 1 comment

Comments

@dougrich
Copy link

dougrich commented Dec 6, 2015

Since the latex is compiled inside a temporary directory, latex commands that reference relative files are not resolved. Examples are include and input.

@rreusser
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants