You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 for lazy.nvim):
@12425 This feature was added in PRs: #252 and #344, make sure you have the latest version of the plugin.
" Not necessary to set enabled to true, as long as it's not set to false.
" let g:codeium_enabled = v:true
let g:codeium_filetypes_disabled_by_default = v:true
let g:codeium_filetypes = {
\ "rust": v:true,
\ "typescript": v:true,
\ }
The wildcard syntax could've been a good implementation option though :)
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: