-
Notifications
You must be signed in to change notification settings - Fork 42
Error when PDF viewer is already open #252
Comments
Thank for the issue report! Unfortunately there is no way for us to detect and close SumatraPDF unless we resort to DDE as detailed in #119. At this point we are not planning on adding such a feature because of significant implementation issues. |
This is a new issue for me, I used atom-latex with Sumatra with no issue for close to a year. It happened after updating atom-latex and switching over to latexmk. |
After updating atom and atom-latex on my Mac, I get the same error. However I now get the error even if Skim is closed. If I use pdf-view then there is no error. I wouldn't mind the error so much if it did not overriding the latex warnings, as it doesn't seem to be effecting the build/opening of the PDF. To that end I commented out line 16 in /lib/opener.js and everything seems to be running smoothly. Would it be possible to append the error message to the latex log file instead of overriding it at the bottom of the screen? |
The Skim error is a bug in their SyncTeX. Is has been reported and will fixed in the next version. |
So are the Sumatra and Skim errors totally unrelated even though the error message is the same? Or is it possible the Sumatra error is related to SyncTex as well? |
They are probably unrelated. I'll have to get on Windows machine to see if I can reproduce the Sumatra issue at some point. |
But even if I can, we probably won't be able to do much about it since in the past the obstacle has been Sumatra's insistence on DDE messages. |
I just reproduced this. |
If I build my latex file with my PDF viewer (SumatraPDF) already open then I get the following error "An error occurred while trying to run opener (1)." When the error is displayed it doesn't show errors or warnings from the latex log file. The PDF file is created and updated in Sumatra and the window does become selected. If I turn off the option "Open result after successful build" or close Sumatra before building then I no longer get the error and can see the warnings from the Latex log file.
The text was updated successfully, but these errors were encountered: