ecosse3 / nvim

A non-minimal Neovim config built to work most efficiently with Frontend Development
GNU General Public License v3.0
1.24k stars 109 forks source link

Copilot - Codeium #165

Closed gmdevz closed 7 months ago

gmdevz commented 1 year ago

I don't know why when I set the copilot = false in my Ecovim.lua and only set codeium = true. I don't get any autocompletion. Do I really need the Copilot to be enabled to be able to use Codeium and get autocompletion? 🤔

ecosse3 commented 1 year ago

Thanks for the issue! I didn't use codeium daily recently, so I didn't notice it. It should work after https://github.com/ecosse3/nvim/commit/07629b5b730012ef180149158d8bc07cf6881104 on dev branch.

You need to reload nvim & "Update Plugins" after change in EcoVim.lua. Also, make sure to run :Codeium Auth command to get the token.

I noticed that sometimes you need to click again to get Codeium autocompletion. It may be a bug in cmp and I cannot fix it at this moment. Please don't hesitate to open PRs.

al77ex1 commented 1 year ago

I have same as problem. I have token in config file for codeium plagin in cache. This issue appear when I set option 'copilot = false'
if I just restore option value to 'true' - autocompletion works fine with codeium plugin.

Pkcarreno commented 11 months ago

This is not just a Codeium issue, I was playing with this for a bit. For some reason, when disabling Copilot, the entire autocompletion breaks. To test it just disable Copilot (without enabling other AI) and autocompletion stop working.

I still trying to figure out why this happened, https://github.com/ecosse3/nvim/commit/07629b5b730012ef180149158d8bc07cf6881104 seems to not make any difference.

I update here if I find something

Pkcarreno commented 11 months ago

This is not just a Codeium issue, I was playing with this for a bit. For some reason, when disabling Copilot, the entire autocompletion breaks. To test it just disable Copilot (without enabling other AI) and autocompletion stop working.

I still trying to figure out why this happened, 07629b5 seems to not make any difference.

I update here if I find something

Dev branch working properly* I hadn't tested the entire branch until now