Comment 1:

It's worth pointing out that this is not just for vim, but for any editor that supports
the standard "quickfix" error format.
Unfortunately, it looks like this error is coming via the net/http package (why?), which
is the source of the "http: " prefix. It might be quite tricky to cleanly remove that
prefix except by using some late-stage hacking.

Labels changed: added priority-go1, removed priority-triage.

Owner changed to @rsc.

Comment 3:

Summary change is fine as long as "readable" is in the "machine-readable" sense.

Comment 4:

It is in the human-readable sense.  The error makes no sense to humans either right now.
 The leading http: is because it is complaining about import "http", but no one can
tell.  If I make it human-readable, the dumb machines will understand it too.

Status changed to Accepted.

Comment 5:

Okay, that's a different angle on the same bug, then. The original report was about the
error not being machine readable because of the leading "http: ".
For me, at least, the current error gives me an accurate line number, and I can go see
what's on that line and match it up with "package could not be found locally", so in
that sense it's perfectly human-readable. I can't, however, push the error through vim
and let it take me to the right line automatically, hence it is not machine-readable.
I guess both birds will be killed with the same stone, whether the stone is thrown by a
human or a machine.

Comment 6:

You are focusing on quite possibly the least important problem with
this error.  They will all be fixed.

Comment 7:

The reporter of this issue complained this error mucked up vim's
quickfix; for him, machine-readability was the *only* problem with it.
The same applies to me.

Comment 8:

I said I would fix it.

Comment 9:

You learn something every day.  Quickfix invented the syntax of error messages on Unix.
I had no idea.

Comment 10:

I am not sure why this is still open.  Fixed by the big bug busting CL.

Status changed to Fixed.