Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Annoying warning messages in OSX 10.11 (El Capitan) #148

Closed
taiya opened this issue Apr 17, 2016 · 6 comments
Closed

Annoying warning messages in OSX 10.11 (El Capitan) #148

taiya opened this issue Apr 17, 2016 · 6 comments
Assignees

Comments

@taiya
Copy link

taiya commented Apr 17, 2016

I've upgraded to "El Capitan" and something just became quite worse. I have a document that compiles just fine, but regularly I get the error window popping up and sticking around for a second or two, then it disappears by itself. If I compile the latex document with Command+R there is no problem... this only happens in the "watch document" mode. Furthermore, I cannot even check the log file, as after the message disappears I think the problem is self-resolved (so the log file doesn't contain any error at all)...

This is a snapshot of the problem.
Anybody having the same issue?
(this happens on two different machines, and only after I updated the OS)

screenshot 2016-04-16 21 36 18

@sanssecours
Copy link
Member

Hi Andrea,

thanks for the bug report. This issue should have nothing to do with the operating system you are using. The pop-up shows that latexmk returned a non-zero return code. It looks like the document contains some form of (minimal) error. If you are sure that the document contains no errors, then you can also try to remove all auxiliary files (^ + + ), before you use “Watch document”. Then the pop-up should not show up again, until you save a faulty version of the document.

Can you please send me a (minimal) example document and steps to reproduce the error?

Thank you,
René

@taiya
Copy link
Author

taiya commented Apr 17, 2016

Hi Rene, unfortunately I do not have a minimal example. I am working on a deadline and the working repository is all I have. If you give me an email I can send you a zip (to be kept confidential) and you can try re-compile the project yourself?

@sanssecours
Copy link
Member

If you give me an email I can send you a zip (to be kept confidential) and you can try re-compile the project yourself?

Okay. Please send the files to [email protected].

@sanssecours sanssecours self-assigned this Apr 17, 2016
@taiya
Copy link
Author

taiya commented Apr 18, 2016

Apparently this was my mistake. There was an error inside my .bib file. Can I change my bug report? I'd say that this plugin need to find a better way of intercepting and showing bibtex errors!!!

@sanssecours
Copy link
Member

Can I change my bug report? I'd say that this plugin need to find a better way of intercepting and showing bibtex errors!!!

I opened a new issue: #149

@taiya
Copy link
Author

taiya commented Apr 19, 2016 via email

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

No branches or pull requests

2 participants