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

Problem with javac signalling errors in files other than currently scanned #10

Open
vkazanov opened this issue Jan 6, 2013 · 0 comments

Comments

@vkazanov
Copy link

vkazanov commented Jan 6, 2013

Flymake gives "Configuration error" and switches off if errors are only found in other files than a given one. I.e., it fails when I check my java project with javac, and current file has no errors at all, but one of the dependencies is flawed.

The following hack fixes the problem:

(defadvice flymake-post-syntax-check (before flymake-force-check-was-interrupted)
    (setq flymake-check-was-interrupted t))
(ad-activate 'flymake-post-syntax-check)

I have debugged the "flymake-post-syntax-check" function and found out that it does not normally work with the case. It's either the checking process has a zero exit code or no errors in the current file, or a non-zero exit code and errors in the file. I do not fully understand the meaning of the third case - the one that the hack uses.

Anyway, in my case - non-zero exit code and no errors in the file checked - flymake fails.

PS I am okay with giving more code-related details.

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

No branches or pull requests

1 participant