Closed koppor closed 8 years ago
This is a rather low-level error. Such are caught in a big bucket and assumed to be fatal and unfixable, hence ltx2any stops without looking at what actually happened (which can be any of a myriad of things). Thus, this is intended behaviour.
In your case, since Acrobat Reader locks the file (d'oh) ltx2any can not copy the new PDF in its place. That means you will never see any updates. That's clearly an error that prevents a normal work flow. So I think that stopping is correct in this case, too.
Acrobat Reader + background recompilation apparently don't go together. You need to close the viewer before rebuilding, use another viewer, or use Acrobat only to view a copy. (If you have another fix, I'm all ears.)
Normally, I'm using Sumatra PDF because of this. I only quickly clicked on the PDF and run ltx2any and wondered whether there is an easy workaround.
System: Windows 10
When I open the PDF file with Acrobat Reader, it is write locked.
When runnig ltx2any.rb, I get following output:
Expected behavior: