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
If the PDF output file already exists, the current behavior of latexmk_emu() is to rename the existing file and to move it back if the compilation failed.
This causes problems with workflows that use an external PDF viewer that monitor changes to the PDF file. For example, Skim on macOS will retain a pointer to the existing file (which is invariant to the renaming) and not see the newly compiled file. This also prevents the existing file from being removed.
Instead, can the behavior of latexmk_emu() be changed so that the output destination is given a temporary name, and then upon successful compilation the result is copied on top of the existing file?
The text was updated successfully, but these errors were encountered:
If the PDF output file already exists, the current behavior of
latexmk_emu()
is to rename the existing file and to move it back if the compilation failed.https://github.com/yihui/tinytex/blob/c7d62e178915e56728c7b591f4baa0d0f4874c26/R/latex.R#L135
This causes problems with workflows that use an external PDF viewer that monitor changes to the PDF file. For example, Skim on macOS will retain a pointer to the existing file (which is invariant to the renaming) and not see the newly compiled file. This also prevents the existing file from being removed.
Instead, can the behavior of
latexmk_emu()
be changed so that the output destination is given a temporary name, and then upon successful compilation the result is copied on top of the existing file?The text was updated successfully, but these errors were encountered: