-
Notifications
You must be signed in to change notification settings - Fork 365
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
Test multiline error messages #15
Comments
I currently have this problem with the Kibit Clojure code analyzer. I'm using these settings to parse multiline messages:
Kibits output:
As you can see, the last line gets lost. |
Yup. I did some investigation, and it looks like multiline messages will work fine, as long as the whole message comes through in the same stdout/stderr event. If it gets split across events, it will mess up the parsing of the message. The best solution I can think of is to make a setting to gather all the maker output before trying to put it in the loclist or quickfix list. |
This feature should be added in e1bce3d. Try adding |
Works now as expected. Thanks! |
Unless setting buffer_output, multiline errorformats seem to be parsed unreliable. Appareantly it only works when both lines come trough the same event (neomake/neomake#15).
I suspect that multiline error messages will not work currently. We may need to join all lines back into a string with newlines before we feed it to the location/quickfix list. We may also need to gather all errors until the job completes before we populate the list for some checkers.
The text was updated successfully, but these errors were encountered: