-
-
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
g:go_metalinter_command
does not override the command.
#1622
Comments
I can duplicate this. As far as i see in code For me bether solution is to change this to |
I don't stick to replacing a command. For your reference, ALE has some options for gometalinter like below.
|
I saw the function go#lint#Gometa, but it's ... confused...
It needs to be refactored. |
@kyoh86 some of the issues you noticed are resolved in #1640. For the others:
|
i know...but why is the case excepted? |
It's not clear to me if that was an intentional decision or not. The docs, though, say that |
…inter-command Fix overriding metalinter command (fix #1622)
What did you do? (required. The issue will be closed when not provided.)
Wrote
let g:go_metalinter_command = "gometalinter --config=" . $HOME . "/.gometalinter/config.json"
What did you expect to happen?
gometalinter called with an argument,
--config=$HOME/.gometalinter/config.json
What happened instead?
gometalinter called with arguments,
--disable-all
gometalinter
--config=$HOME/.gometalinter/config.json
Configuration (MUST fill this out):
:version
):go version
):go env
):commit:
f4b4ba13f95883cbb4f7c43b871a480932614e0f
vimrc
you used to reproduce (use a minimal vimrc with other plugins disabled; do not link to a 2,000 line vimrc):The text was updated successfully, but these errors were encountered: