ticket.vim VS dressing.nvim

ticket.vim

I use ticket.vim.

Frequency Sorting for vim.ui.select: Now you can enjoy (f)recency-based sorting for pickers started through vim.ui.select, provided by dressing.nvim or (untested) telescope-ui-select.nvim. For this to work, make sure to load telescope-all-recent.nvim AFTER dressing.nvim.

For 2, I use dressing.nvim with the options below (requires telescope) and that gives me a nice UI for code actions which you can exist out of. lua { input = { enabled = false }, select = { telescope = require("telescope.themes").get_cursor() }, }

cool, thanks, solved my problem, just checked the codebase again with the vim.ui.select, found the plugin stevearc/dressing.nvim

Dressing works, but most of its code deals with vim.ui.select, which seems slightly overkill here.

In general, vim.ui.input does not seem to be super completion friendly, it seems the only method currently available is to use dressing, cmp, and cmp_omnifunc to get some basic completions that are provided by omnifunc: https://github.com/stevearc/dressing.nvim/issues/55

Are you using https://github.com/stevearc/dressing.nvim by chance??? It's awesome to see ui plugins emerging that can be used in other plugins :)

I wrote this little guy which promots you for your query with vim.ui.input, which is really neat if you have a plugin like dressing.nvim installed

it uses vim.ui.select so you can use for example dressing.nvim to use telescope for the UI.

I wanted to share a little utility function, I believe is quite useful. It takes a command as input and shows the output in a scratch buffer. Inputting “scratch” will open an empty scratch buffer, command completions are enabled. It is based on the builtin vim.ui.input prompt, which can be automatically styled by the excellent dressing.nvim. I often use it to open the current colorscheme’s highlight groups in a buffer, with the advantage that colorizer plugins will work then. Or you can check out the latest messages when you got errors in your config, etc. Just don’t try to update your operating system through it…

the little bit of indirection with save_file is required because vim.ui.input might be async (for example if want you're able to use stevearc/dressing.nvim with this snippet without out any modification)