Iordanis Petkakis

@mirsella Yes, what you're suggesting is more in line with other LazyVim completions. Although, personally, I'll be changing that in my config if I end up using the Extra because...

No, I'm not talking about this. I'm talking about something like [this](https://github.com/dpetka2001/dotfiles/blob/ca6bff6219348b95866502584ee75b206a5b4274/dot_config/nvim/lua/plugins/coding.lua#L97-L110), so I can directly enable/disable it via API commands.

`codeium.vim` supports as well. You can see the commented out sections that are `codeium.vim` equivalent. `codeium.nvim` does not support it (I think?? Except if I'm wrong), since it's a source...

I haven't used supermaven for about a 1+ month, so no idea about latest progress. When I used it, it was still a bit rough around the edges. So, my...

I believe the mappings for Telescope should go under `keys` in Telescope spec instead of `keymaps.lua`, because there is also `fzf-lua` alternative (that quite a few users use), in order...

No idea. I don't use Telescope. I've switched to `fzf-lua`. Just make a PR that adds this keymap under Telescope `keys` and leave the rest of default keymaps as is....

I believe in `fzf-lua` the corresponding command is `FzfLua quickfix_stack`, but I don't use it that much. Just leave it be. It's just one keymap and users can add it...

Is this really worth an Extra with just 4 lines of configuration? Also, you're specifying the LSP server in `mason.ensure_installed`, but you're not setting up the LSP server in `nvim-lspconfig`....

Does the default codeaction (`ca`) give anything different than RustLSP("Codeaction")? If not maybe we could just skip the latter?

No idea, I'm not doing Rust and don't know what the preferable way would be. Maybe wait for the maintainer's feedback on this one. Maybe changing the mapping into something...