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

Create all auxiliary files in the directory specified by -aux-directory without ever writing in the source directory #785

Closed
giuliofoletto opened this issue Apr 19, 2021 · 3 comments
Assignees
Labels
Milestone

Comments

@giuliofoletto
Copy link

The MiKTeX implementation of pdflatex provides the neat -aux-directory option which specifies where to put auxiliary files. Despite this, if SyncTex is enabled (-synctex=1), the synctex.gz file is temporarily created in the source directory, and then moved to the auxiliary directory only at the end of compilation.

Feature request: Create this auxiliary file directly in the auxiliary directory, without ever writing in the source directory.

Although this would be irrelevant to most, in some use cases, the source directory must be protected from writing, or is watched by other processes which spin up uselessly if the temporary files are created and deleted frequently.

P.S. I hope this is the right place to ask for this. I ask here because as far as I know only MiKTeX provides the -aux-directory option.

@edocevoli
Copy link
Member

The synctex.gz file is an output file, so -aux-directory has no effect. You must use -output-directory.

@giuliofoletto
Copy link
Author

Sorry, I did not realize that. However, the problem still stands. I am using -output-directory and the synctex.gz file gets created in the source directory, and then moved to the specified directory at the end of compilation. Should I create another issue with more precise wording?

Basically, the feature request would be: Create this output file in the directory specified in -output-directory instead of moving it there after writing to the source directory.

If you think this is a bug, and not a missing feature, I can file the issue as a bug with the complete bug reporting procedure. Let me know.

@edocevoli edocevoli reopened this Apr 24, 2021
@edocevoli edocevoli self-assigned this Apr 25, 2021
@edocevoli edocevoli added this to the 21.5 milestone Apr 25, 2021
@edocevoli edocevoli added the bug label Apr 25, 2021
edocevoli added a commit that referenced this issue Jun 2, 2021
@edocevoli
Copy link
Member

Thank you, this has been fixed with v21.6.

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

No branches or pull requests

2 participants