Jit

Thanks for the bug report! I currently don't have a Windows environment set up so I won't be able to debug this. I'll try to get one up running shortly.

I can reproduce this. Renderer has to be using a floating window (e.g. `wildmenu_renderer` with `mode: 'float'` or `popupmenu_renderer`). This is a Neovim bug, see https://github.com/neovim/neovim/issues/15280. A workaround is to...

I can't reproduce this. Could you elaborate on what it means to `turn off` file3? Or list the steps in terms of `:e file1`, `:bdelete file1`, etc.

This is blocked by the bug mentioned in https://github.com/neovim/neovim/issues/15280.

Thanks for using the plugin! Could you help provide more details? e.g. - `:version` output - Any error messages in `:messages` - A minimal `init.vim` to reproduce this if possible...

Hi, do you have any updates on this?

For the `wildmenu_renderer`, you have to set the devicons via the pipeline. ```lua wilder.set_option('pipeline', { -- your pipeline here wilder.result_draw_devicons(), }) ``` The `result_draw_devicons()` function is meant to be deprecated,...

Thanks for the detailed info and the screenshots! I've narrowed this down to `command DiffviewOpen` setting a Lua function for the `complete` option. I don't see a way to call...

`wilder` gets the candidates from the command completion manually: https://github.com/gelguy/wilder.nvim/blob/777b163e394ba658ef288292efb533b25610ef9d/autoload/wilder/cmdline.vim#L681-L682 It doesn't handle Lua functions sincce `complete=lua` was (relatively) newly added. Furthermore, Lua functions are stringified to ``, and so...

Hmm, looks like I'm wrong - `wilder` is already using the `getcompletion(..., 'cmdline')` fallback, but is setting the wrong argument for the fuzzy filter. (`wilder` basically doesn't handle `complete=` correctly.)...