Did you upgrade to latest plugin version?
Yes
Did you upgrade to/compile latest binary? Run shell command
Yes
bin/languageclient --version to get its version number.
languageclient 0.1.156 90e49e587fc700c81cd21529e773b7f863dfc958
(Neovim users only) Did you check output of :checkhealth LanguageClient?
OK
Did you check [troubleshooting]?
Yes
A clear and concise description of what the bug is.
After updating to the latest version in dein.vim, the title error occurred.
nvim --version or vim --version):NVIM v0.4.3git rev-parse --short HEAD):90e49e5bin/languageclient --version):set hidden
set completeopt=menu
set signcolumn=yes
let g:LanguageClient_useVirtualText = 0
let g:LanguageClient_autoStart = 1
let g:LanguageClient_loadSettings = 1
let g:LanguageClient_serverCommands = {
\ 'rust': ['~/.cargo/bin/rustup', 'run', 'stable', 'rls'],
\ }
let $RUST_BACKTRACE = 1
let g:LanguageClient_loggingLevel = 'INFO'
let g:LanguageClient_virtualTextPrefix = ''
let g:LanguageClient_loggingFile = expand('~/.local/share/nvim/LanguageClient.log')
let g:LanguageClient_serverStderr = expand('~/.local/share/nvim/LanguageServer.log')
Steps to reproduce the behavior:
$ git clone -b getting-started https://github.com/nabezokodaikon/rust-study.git$ cd rust-study/ch03/bitonic-sorter$ nvim src/first.rs23:50:15 WARN unnamed src/language_server_protocol.rs:2389 Failed to start language server automatically. invalid type: integer0, expected string or map
LanguageClient does not start.
LanguageClient starts.
It worked with tag v0.1.153.
I was just about to click new issue button :) Same problem here. I rolled back one commit back (d273439c1c05a599423c278fcad95df6564d7b8a) language server starts without any problem.
There was a breaking change regarding the LanguageClient_useVirtualText option, it now takes a string instead of a number. See https://github.com/autozimu/LanguageClient-neovim/blob/next/doc/LanguageClient.txt#L343 for the accepted values.
There was a breaking change regarding the
LanguageClient_useVirtualTextoption, it now takes a string instead of a number. See https://github.com/autozimu/LanguageClient-neovim/blob/next/doc/LanguageClient.txt#L343 for the accepted values.
Thank you! Confirmed to work!
There was a breaking change regarding the
LanguageClient_useVirtualTextoption, it now takes a string instead of a number. See https://github.com/autozimu/LanguageClient-neovim/blob/next/doc/LanguageClient.txt#L343 for the accepted values.
This also broke for me. If we broke backwards compatibility shouldn't there be more transparency (in the changelog or error code)?
Most helpful comment
There was a breaking change regarding the
LanguageClient_useVirtualTextoption, it now takes a string instead of a number. See https://github.com/autozimu/LanguageClient-neovim/blob/next/doc/LanguageClient.txt#L343 for the accepted values.