zbirenbaum
Multiple offset encodings warning when used with clangd
In C++ files when clangd is attached and copilot.lua is loaded, a repeated warning about Multiple offset encodings occurs. This seems to be a common issue as well when using null-ls at the same time as clangd but the fixes used for that do not seem to work with copilot.lua.
Can you provide more details about how to reproduce it? I don't use clangd for my day job, and unless you give me exact steps to reproduce the issue I can't help.
To reproduce, load copilot.lua and let clangd attach itself to a buffer. The below warning then repeatedly pops up for any cursor change or edit whether inside Insert mode or outside. When I do :Copilot disable, this stops occurring.
To reproduce, load copilot.lua and let clangd attach itself to a buffer. The below warning then repeatedly pops up for any cursor change or edit whether inside Insert mode or outside. When I do :Copilot disable, this stops occurring.
Got the same warning!
This isn't an copilot.lua issue.
https://github.com/jose-elias-alvarez/null-ls.nvim/issues/428
The problem ariese because two clients copilot and clangd using different offset_encoding attached to same buffer, solution proposed in the thread is to either change clangd's or in this case copilot offset encoding. By default, clangd uses utf-32 offset encoding.
This isn't an
copilot.luaissue.jose-elias-alvarez/null-ls.nvim#428
The problem ariese because two clients
copilotandclangdusing differentoffset_encodingattached to same buffer, solution proposed in the thread is to either change clangd's or in this casecopilotoffset encoding. By default, clangd usesutf-32offset encoding.
by any chance, do you know how to change the offset for copilot?
