lsp-completion-at-point
short-circuits the completion function chain
#4386
Labels
lsp-completion-at-point
short-circuits the completion function chain
#4386
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
After adding my own function to
completion-at-point-functions
it turns out thatlsp-completion-at-point
shortcuts the completion function chain when it does not find any completions of its own.A completion at point-function can return nil to pass on the completion, allowing the next completion function in line to try. I think maybe
lsp-completion-at-point
always returns a lambda, which then would short-circuit the others in the list.One way to work around that would be to ensure that lsp-mode appends instead of prepends its function to the list. Now it places itself in front of everything else, blocking them.
Steps to reproduce
Expected behavior
If lsp-mode can't complete, let the other completion functions have a go - OR wait with lsp-mode completions until the end.
Which Language Server did you use?
Not relevant.
OS
MacOS
Error callstack
No error call stack.
Anything else?
I realize the way lsp works might not mesh very well with how emacs completion works. I would assume that is why it is not being a "good citizen" with the other completion functions in the list. Maybe an option would be to move lsp-completion to the end of the chain.
The text was updated successfully, but these errors were encountered: