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

An error occured while trying to run opener (1) - SumatraPDF 3.1.2 #282

Closed
moospit opened this issue Oct 27, 2016 · 4 comments
Closed

An error occured while trying to run opener (1) - SumatraPDF 3.1.2 #282

moospit opened this issue Oct 27, 2016 · 4 comments

Comments

@moospit
Copy link

moospit commented Oct 27, 2016

I use latex with SumatraPDF as viewer. When compiling a document the first time SumatraPDF opens up just fine. Rebuilding (no matter if changes made to the document) results in the message:

An error occured while trying to run opener (1)

If changes have been made SumatraPDF displays them just fine, but i don't get any other errors or warnings from the build process. SyncTex seems to work just fine.

Versions:

  • latex: 0.38.1
  • atom: 1.11.2
  • SumatraPDF: 3.1.2
@thomasjo
Copy link
Owner

I think this is a known problem. We're aware that the SumatraPDF opener is a bit wonky, but that is, as far I as know, caused by weirdness with SumatraPDF itself. I guess until we figure out how to work around the issues with SumatraPDF, we might have to silently ignore the returned exit codes (or possibly loging them as info messages instead of just silently ignoring them).

/cc @yitzchak

@yitzchak
Copy link
Collaborator

@thomasjo I have cleaned up SumatraOpener and tried every combination of arguments I can think of. Nothing makes a difference. Currently, the error is ignored in master. It is possible to turn it into an info message, but not easily because the error is generated after latex.log.groupEnd is called. Therefore, recording the error (whatever the severity) clobbers the current messages resulting from LogParser.

TL;DR It's fixed in the next version by ignoring Sumatra's weirdness.

@karyon
Copy link

karyon commented Oct 28, 2016

for the record, as mentioned in #250, i get this whenever the document compiles without errors and clicking on the "latex log". when there are errors, clicking on it actually opens a small pane that shows errors and warnings.

@yitzchak
Copy link
Collaborator

This we be resolved in the next version.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants