-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fix go build error parse #1716
Fix go build error parse #1716
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1716 +/- ##
==========================================
+ Coverage 19.57% 23.82% +4.25%
==========================================
Files 57 57
Lines 4787 4784 -3
==========================================
+ Hits 937 1140 +203
+ Misses 3850 3644 -206
Continue to review full report at Codecov.
|
|
Parse go build errors using the same errorformat as is used by vim7.4 so that the column will be included in the quickfix error instead of being part of the error message itself.
41b3169
to
f916e1e
Compare
☝️ fixed. |
lgtm |
Errors from
:GoBuild
were including the column number in the quickfix error'stext
message instead of it parsing it into in the quick fix error'scol
field, becauseerrorformat
wasn't being using used parse the errors whengo build
was run asynchronously.This PR uses
go#list#Parse
to parse the errors so that the result in vim8 and Neovim is the same as it is in vim7.4.While I was at it, I added a test for
:GoVet
and modified it to also usego#list#Parse
.