Double #include insertion with clangd
#72
Comments
|
Looks like a bug. I will investigate tomorrow. |
girishji
added a commit
that referenced
this issue
Aug 6, 2024
LSP client If `completionTextEdit` is set in LSP client (https://github.com/yegappan/lsp), it applies LSP supplied text changes twice -- once, when completion candidate is accepted and second time after `CompleteDone` event is fired. This seems like a LSP client bug. Solution: Set completionTextEdit to `false` in LSP client config. #72 #37 M autoload/vimcomplete/lsp.vim
|
This looks like LSP client issue (yegappan/lsp#545). In the meantime, you can set |
|
That worked for me with your latest commit. Are there any undesirable side effects of setting |
|
This is a LSP issue. The undesirable side-effect is for typescript server (and others maybe) that make text edits available at a later time. They will not apply text edits. I have opened an issue in LSP, and it needs to be tracked there. This plugin should not set or unset |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, there. When using
clangdas my language server with https://github.com/yegappan/lsp, strange behavior is observed:① If I select a completion entry and press
<Esc>, the corresponding#includefor that entry is inserted (which is surprising).② If I select a completion entry and press,
<c-y>, the corresponding#includefor that entry is inserted twice. (Additionally, the function signature is entered, but that may just be aclangd"feature.")Here's a brief video:
https://github.com/user-attachments/assets/4b948808-c992-467b-b5a1-07c843a01334
The text was updated successfully, but these errors were encountered: