-
-
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
GoRun shows a blank line in quickfix window when panic is received #2328
Comments
vim-go won't parse the panic output, because there isn't a reliable way to tell non-panic output from the panic output, especially if there's a substantial output. vim-go really shouldn't show any errors unless the exit code from |
Can we at least then show a generic message in the quickfix window line, such as I actually noticed that vim-go showed the line, where the runtime error occurred while writing this issue. |
Yes. I'm planning to refactor the |
Capture error messages from panic. I'm not 100% sure that this is the right course of action. It might be better to treat panics as successes, because non-zero exit status from go run are generally discarded except for compiler errors. This change is inconsistent with that fact and may lead people to expect that non-zero exit statuses from the command being run should always populate the quickfix list. Fixes fatih#2328
What did you do? (required: The issue will be closed when not provided)
Given the following source file:
I typed
:GoRun
.What did you expect to happen?
Quickfix window opens with line that failed + output showing the panic.
What happened instead?
Quickfix window opens with a blank line & pointer to line that failed.
Configuration (MUST fill this out):
vim-go version:
vim-go @ 3e9a292
vimrc
you used to reproduce (use a minimal vimrc with other plugins disabled; do not link to a 2,000 line vimrc):vimrc
Vim version (first three lines from
:version
):NVIM v0.3.4
Build type: Release
LuaJIT 2.1.0-beta3
Go version (
go version
):go version go1.11.4 linux/amd64
Go environment
go env
Output:The text was updated successfully, but these errors were encountered: