Skip to content
This repository has been archived by the owner on Aug 14, 2022. It is now read-only.

Error when PDF viewer is already open #252

Closed
justinriddoch opened this issue Oct 11, 2016 · 8 comments · Fixed by #265
Closed

Error when PDF viewer is already open #252

justinriddoch opened this issue Oct 11, 2016 · 8 comments · Fixed by #265

Comments

@justinriddoch
Copy link

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.

@yitzchak
Copy link
Collaborator

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.

@justinriddoch
Copy link
Author

justinriddoch commented Oct 13, 2016

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.

@justinriddoch
Copy link
Author

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?

@yitzchak
Copy link
Collaborator

The Skim error is a bug in their SyncTeX. Is has been reported and will fixed in the next version.

@justinriddoch
Copy link
Author

justinriddoch commented Oct 18, 2016

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?

@yitzchak
Copy link
Collaborator

They are probably unrelated. I'll have to get on Windows machine to see if I can reproduce the Sumatra issue at some point.

@yitzchak
Copy link
Collaborator

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.

@yitzchak
Copy link
Collaborator

I just reproduced this.

@yitzchak yitzchak reopened this Oct 19, 2016
@yitzchak yitzchak mentioned this issue Oct 22, 2016
4 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants