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

Handle output_directory and change_directory properly #8

Merged
merged 2 commits into from
Dec 19, 2021

Conversation

atticus-sullivan
Copy link
Contributor

@atticus-sullivan atticus-sullivan commented Dec 13, 2021

If option change_directory is used output_directory should be relative
to the new pwd (in current implementation that would be . always) or
use absolute path. In addition if option change_directory is used flag
-output-directory doesn't need to be set on the tex compilation
command.

This implements this behaviour by setting options.output_directory to
nil (so that -output-directory will not be set later) after
generating the init lua script.

Addresses #7

I'm not quite sure about the options.output_directory handling. Maybe it would be nicer if tex_engine would respect the change_directory option to achieve a more consistent tex_options. On the other hand having a change_directory option for tex_engine just to avoid setting the -output-directory flag on the tex command isn't that nice either.

I hope these are all spots which were causing the change_directory trouble.

If option change_directory is used output_directory should be relative
to the new pwd (in current implementation that would be `.` always) or
use absolute path. In addition if option change_directory is used flag
`-output-directory` doesn't need to be set on the tex compilation
command.

This implements this behaviour by setting `options.output_directory` to
`nil` (so that `-output-directory` will not be set later) after
generating the init lua script.
@minoki minoki merged commit 9fa6c18 into minoki:master Dec 19, 2021
@minoki
Copy link
Owner

minoki commented Dec 19, 2021

Merged. Thank you for the contribution!

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

Successfully merging this pull request may close these issues.

2 participants