-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Plugin is not working #19
Comments
Should be problem of your language server, checkout https://github.com/neoclide/coc.nvim/wiki/Debug-language-server#using-output-channel |
Can I clarify this: I thought I do not need to if I install it as an extension via I have added like this:
:CocOpenLog still shows the same. |
not working |
Also wondering: is this deprecated/not supported anymore? If so, I would have to move over to ALE to support Yaml linting |
No.
I don't see a problem in your logs. Can you please tell us what you're trying to do or what is not meeting your expectations? |
The problem I am facing is that, if I have a file that is not valid yaml, it does not warn me or raise an error. |
@esn89 - can you provide an example yaml? I use coc-yaml and it reports warnings and errors for me. |
Here you go:
I expect it to highlight "asdfa" since it isn't really valid. And to highlight the missing bracket after "finished". And the
|
Seems to be working for me.
ScreenshotsVimVS Code |
Could you show me your vimrc and :CocConfig please? |
Here is my coc-related vimrc. |
@pbnj Thank you, I will try to tinker around and make it work. |
Still no luck, do you mind letting me know your nvim version and yaml-language-server version? |
I'm on vim
And on coc-yaml: |
Nevermind, I found the error, it was my fault. I was experimenting with ale and had this in my coc-settings.json: I deleted it and it works. |
nvim version:
Using coc-yaml@1.0.4
When I have a .yaml file open in vim, I check the process tree (ps aux | grep yaml) and I see the server.js start:
Output of
:CocOpenLog
:And this is what my
:CocConfig
looks like:Any help would be appreciated.
The text was updated successfully, but these errors were encountered: