-
-
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
Show full error messages from GoRename #566
Labels
Comments
Hi @kalafut This is a great catch. Right now we don't do any kind of error message parsing for GoRename. Could you please paste some error message examples that I can check? Also a test case (repo maybe) where I can test it would be helpful. |
I've created a gist of a sample file that causes this type of error. |
fatih
added a commit
that referenced
this issue
Oct 18, 2015
This fixes #566 and also introduces parsing errors for `:GoRename` command. Now it's acting like our other commands such as `:GoTest`, `:GoBuild`, etc.. It fully parses the errors and jumps to the first error it founds.
Just tried it out and it seems to work fine. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
gorename "conflict" and "reference will become shadowed" errors (and maybe others) list the conflict points on multiple lines. vim-go only shows the first line of the output which usually doesn't haven't anything helpful. During complex refactors, I find myself running gorename on the command line to get at the full error message. It would be good if the plugin expose the full output.
The text was updated successfully, but these errors were encountered: