Closed devcharmander closed 1 year ago
Closing this issue as this seems like a duplicate of this https://github.com/Exafunction/codeium.el/issues/20
Will reopen otherwise :)
It worked!
Writing it here if someone stumbles up on this issue.
Since there were multiple backends, the value of the variable completion-at-point-functions
should have codeium-completion-at-point
on the top of the list.
The easy way to do it was to use cape which was also mentioned in the Readme file.
I'm really glad you found an easy solution, but would you mind documenting it a bit further for us in the back. I feel like I have tried several permutations, and haven't found the winning one yet.
I have turned off LSP, which works, but isn't ideal. I have enabled cape and used the hook as configured in this README with:
(add-hook 'python-mode-hook
(lambda ()
(setq-local completion-at-point-functions
(list (cape-super-capf #'codeium-completion-at-point #'lsp-completion-at-point)))))
Which somehow leaves lsp earlier in the completions-at-point-functions
list. I attempted the add and remove functions in the linked issue, which seemed to work but seems a bit heavy handed since it will require quite a bit of configuration for each mode.
What I'd like is to have codeium at the head of all completions lists in some modes. But I'm failing to see how to force the issue.
I've been struggling to get this running with the setup mentioned in the README.
I use Doom Emacs with Company.
Step 1
Added the above line in my
packages.el
Step 2
Copy pasted the configuration present in the README
Step 3
Codeium-install
-> entered keyCodeium logs
Codeium Diagnose
Expected result:
Start seeing suggestions as I type code.
Actual result:
side by side view of the code and the
codeium-logs