fine-cmdline.nvim VS nvim-mapper

I have fine-cmdline.nvim. It does what I need but it doesn't the UI I want. Is basically a floating input, nothing fancy.

In your reply you mentioned that users can create plugins with "better" ui for cmdline and link to https://github.com/VonHeikemen/fine-cmdline.nvim

fine-cmdline.nvim, enter ex-commands in a floating input (uses nui.nvim).

Potentially https://github.com/VonHeikemen/fine-cmdline.nvim?

For the command line area there is fine-cmdline. Haven't used it personally.

There isn't. Not a real pretty command palette anyway. There is fine-cmdline, but that just offers you a floating input.

Although I remember I saw fine-cmdline, maybe that's what you're looking for (I haven't tried it myself)

I've been using it for a few weeks and other than not being able to see the command line (which can be solved with another plugin), it's basically perfect.

In fine-cmdline I use an on_change event (provided by nui.nvim's input) to manipulate an internal variable in realtime. It's what's makes possible "smart history search".

fine-cmdline.nvim is the plugin.

check out https://github.com/lazytanuki/nvim-mapper, but it takes some discipline to keep all the mappings up 2 date (having a helper function to do mappings helps though)

Add tags (like the "category" option in lazytanuki/nvim-mapper but accepting an array and taking advantage of the nestability of your project. Examples: having the "Motion" tag on anything that operates on a provided motion, LSP tag for LSP maps etc.