-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
ccls - warning: multiple different client offset_encodings detected for buffer, this is not supported yet #2709
Comments
should be solved in nightly can you try latest version |
By nightly, do you mean the latest commit of nvim-lspconfig? I've pulled up to deade69 just now but it still gives the same error. |
neovim latest build |
I changed Neovim to the current nightly tag. At the time of writing it's
My nvim-treesitter was a bit out of date so I updated that too, to nvim-treesitter/nvim-treesitter@90581ac. nvim-lspconfig is also at its latest commit, deade69. With the same configuration posted above, I still get the |
I am having the same issue. |
Same here. |
Looks like it's hard-coded into ccls: Search queries: |
I am having this problem but for clangd. Has this been firgured out for clangd? I tried setting up the capabilities to utf 16 but it still pritns out the error message. |
For clangd, you'll want to refer to this other issue #2184. This issue is for ccls. Short answer though - clangd already has a setting for encoding, located here: https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#clangd. And https://www.reddit.com/r/neovim/comments/18cb9d8/comment/kc9lre2/?utm_source=share&utm_medium=web2x&context=3 Btw the reason I was getting this warning
I think was because at the time I was using null-ls at the same time as ccls. The two plugins were specifying different encodings which led to the warning. However I later moved onto nvim-lint. Somewhat against my will, I still miss null-ls. Apparently there's also none-ls but I haven't looked into whether that plugin has the same encoding bug |
Description
When using nvim-lspconfig with ccls (note, not clangd), I get the following message:
warning: multiple different client offset_encodings detected for buffer, this is not supported yet
There's been a past issue about this with clangd here, #2184 and the server configuration documentation mentions, for clangd, to use "default capabilities, with offsetEncoding utf-8" but it's unclear to me how to apply the same advice to fix this for ccls. Could someone advise on what configuration is needed to fix this pretty spammy warning?
Neovim version
NVIM v0.9.0
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-10 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wvla -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -fno-common -Wno-unused-result -Wimplicit-fallthrough -fdiagnostics-color=always -fstack-protector-strong -DUNIT_TESTING -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -I/__w/neovim/neovim/.deps/usr/include/luajit-2.1 -I/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/build/src/nvim/auto -I/__w/neovim/neovim/build/include -I/__w/neovim/neovim/build/cmake.config -I/__w/neovim/neovim/src -I/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/__w/neovim/neovim/build/nvim.AppDir/usr/share/nvim"
Run :checkhealth for more info
Nvim-lspconfig version
8dc45a5
Operating system and version
CentOS 7
Affected language servers
ccls
Steps to reproduce
Actual behavior
Constant warnings about UTF encodings
Expected behavior
Normal LSP behavior
Minimal config
LSP log
https://gist.github.com/ColinKennedy/1e0afe0158751bb9947902c831fdbe08
The text was updated successfully, but these errors were encountered: