Why are auto completion's candidates different with dabbrev-completion? #398
-
I know in order for dabbrew-completion to work properly, I need to set up lsp-mode #369 for it. But why does auto completion popup work by default? It provides not only candidates that are already in the buffer, but also more than that like in an IDE. Is it expected? Why does auto completion work by default for additional candidates without additional configurations or packages? Here's the screenshot of auto completion If so, how can I make the two consistent with each other? Here's my config:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I see, by default, the auto completion of corfu, only works for elisp source files without further configuration. I figured it out, I have to bind "completion-at-point" to a key instead of binding "dabbrew-completion", the latter only shows in buffer candidates. Now the results of auto completion and a keybinding with "completion-at-point" are identical by default in an elisp source file. |
Beta Was this translation helpful? Give feedback.
-
dabbrev is for word completion, not for programming completion. |
Beta Was this translation helpful? Give feedback.
I see, by default, the auto completion of corfu, only works for elisp source files without further configuration.
I figured it out, I have to bind "completion-at-point" to a key instead of binding "dabbrew-completion", the latter only shows in buffer candidates.
Now the results of auto completion and a keybinding with "completion-at-point" are identical by default in an elisp source file.