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

miktex update causes issues “go to source/pdf” in TeXstudio #846

Closed
edocevoli opened this issue Jun 13, 2021 · 1 comment
Closed

miktex update causes issues “go to source/pdf” in TeXstudio #846

edocevoli opened this issue Jun 13, 2021 · 1 comment
Labels
Projects
Milestone

Comments

@edocevoli
Copy link
Member

Reported by mbert on StackExchange:

The most recent MiKTeX update 21.6 resolves an issue involving the aux directory that seems to have changed the behavior of -aux-directory=<filename> to place the .synctex.gz files in the auxiliary folder rather than in the output directory (in this case the same location as the TeX file and PDF output since no -output-directory is specified) as it did before the update. This is confusing because in the linked issue, it's explained that SyncTeX files are indeed output files, not auxiliary files.

It would not be a concern except that TeXstudio needs the synctex.gz file in the same location as the TeX and PDF files for "go to source/pdf" to work (explained here). The command I'm running in TeXstudio 3.1.2 is

pdflatex.exe -synctex=1 -interaction=nonstopmode -aux-directory=C:\Users\matthew\math\auxtexfiles %.tex

on Windows 10. Is there a workaround to either tell TeXstudio to look in the auxiliary folder for the SyncTeX files or tell MiKTeX to place SyncTeX files with the TeX and PDF files as it did before the update?

@edocevoli edocevoli added the bug label Jun 13, 2021
@edocevoli edocevoli added this to To do in What's next via automation Jun 13, 2021
@edocevoli edocevoli added this to the 21.6.21 milestone Jun 13, 2021
edocevoli added a commit that referenced this issue Jun 22, 2021
@edocevoli edocevoli moved this from To do to In progress in What's next Jun 22, 2021
@edocevoli
Copy link
Member Author

This has been fixed.

What's next automation moved this from In progress to Done Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
What's next
  
Done
Development

No branches or pull requests

1 participant