You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2025. It is now read-only.
When the vim.ui.* methods were added to Neovim core, I was very excited because as a plugin author I have had the unfortunate experience of wanting to prompt the user for input or selection and needing to write my own specific wrappers for every selection plugin. I copied some of my existing wrappers, refactored them a bit, and released it as dressing.nvim. Since then, adoption has taken off and despite its modest feature set, this became quite possibly my most widely distributed plugin. It's 2025 now, and a lot has changed since the introduction of vim.ui.* in 2021 as part of Neovim 0.6.
These days, every one of the fuzzy selection plugins (telescope, snacks, snipe, fzf) has their own implementation of vim.ui.select built-in. The only value dressing provides is automatically patching them for you, and providing a fallback in case no fuzzy finder is installed. For a long time that has been not enough value to justify this plugin's existence, but I kept it alive because despite the proliferation of vim.ui.select options I hadn't seen a decent implementation of vim.ui.input (if I missed yours, it was an oversight not a slight). But now, that has changed! I had secretly been hoping for something to be added to mini.nvim for a while, but folke came out with snacks.nvim and it contains both a fuzzy vim.ui.select implementation and a good vim.ui.input. Now, at long last, I can say that this plugin has outlived its usefulness and retire it. It no longer makes sense to use an extra plugin just to provide a wrapper that exists elsewhere.
When the
vim.ui.*
methods were added to Neovim core, I was very excited because as a plugin author I have had the unfortunate experience of wanting to prompt the user for input or selection and needing to write my own specific wrappers for every selection plugin. I copied some of my existing wrappers, refactored them a bit, and released it as dressing.nvim. Since then, adoption has taken off and despite its modest feature set, this became quite possibly my most widely distributed plugin. It's 2025 now, and a lot has changed since the introduction ofvim.ui.*
in 2021 as part of Neovim 0.6.These days, every one of the fuzzy selection plugins (telescope, snacks, snipe, fzf) has their own implementation of
vim.ui.select
built-in. The only value dressing provides is automatically patching them for you, and providing a fallback in case no fuzzy finder is installed. For a long time that has been not enough value to justify this plugin's existence, but I kept it alive because despite the proliferation ofvim.ui.select
options I hadn't seen a decent implementation ofvim.ui.input
(if I missed yours, it was an oversight not a slight). But now, that has changed! I had secretly been hoping for something to be added to mini.nvim for a while, but folke came out with snacks.nvim and it contains both a fuzzyvim.ui.select
implementation and a goodvim.ui.input
. Now, at long last, I can say that this plugin has outlived its usefulness and retire it. It no longer makes sense to use an extra plugin just to provide a wrapper that exists elsewhere.My recommendation for replacements:
vim.ui.input
vim.ui.select
The text was updated successfully, but these errors were encountered: