Iordanis Petkakis

Yes, I totally get that. I'm not making any decisions, I'm just a simple user like you. I just pointed out ways to go about this and maintainer will decide....

It's because this PR #5620 is only present on LazyVim HEAD and not on the current stable release yet. If you'd like you can follow LazyVim HEAD instead of stable...

> Just for my understanding then, is the issue that LazyVim sets the sources to empty when disabling the cmdline suggestions? Yes, that was needed before to disable the `cmdline`...

`lazy.nvim` was probably not cloned correctly. That's usually a problem with your git version/configuration in your OS.

You're using `dressing.nvim` for input and you have to pass its filetype, which is `DressingInput` to `blink.cmp`, so that `blink.cmp` is not enabled in that input field.

See also blink's docs for [recipe](https://cmp.saghen.dev/recipes#disable-per-filetype) how to disable per filetype.

You have to disable blink in the types of input that you want. Blink's default configuration only disables it in prompt buffers. You have to configure it on your own...

I don't share the same opinion, since every plugin uses a different filetype for the input prompts it uses (be it Telescope, dressing or whatever else). It's up to the...

To add to this, I also noticed that when you have `mini.pairs` enabled with option `modes = { command = true }` it also doesn't show the pair of parenthesis...

So, I tried testing something. I created an autocmd ```lua vim.api.nvim_create_autocmd("CmdlineChanged", { group = vim.api.nvim_create_augroup("update_search_redraw", {}), desc = "Update search redraw", callback = function() vim.schedule(function() vim.cmd("redraw") end) end, }) ```...