New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disabled by default, but respecting BufferEnable? #324
Comments
+1 for this, I also like to disable Codeium in all buffers except a few file types. Currently I'm doing this in vim9 as workaround
These don't work
|
@12425 This feature was added in PRs: #252 and #344, make sure you have the latest version of the plugin.
The wildcard syntax could've been a good implementation option though :) |
@zArubaru Great, it works now! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I wish to start with Codeium disabled globally, but to still allow me to enable it on a buffer-by-buffer basis. I thought
vim.g.codeium_enabled = false
would do it, but after experimentation and delving into code, it seems that both global and buffer settings must be non-disabled. I would have expected that either of them being enabled would enable completion. In the end, starting off as enabled and setting a disabler autocommand seems to have worked (example forlazy.nvim
):Is this the intended way to do it, or am I missing something simple?
The text was updated successfully, but these errors were encountered: