fine-cmdline.nvim VS neovim

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.

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.