Post

I am happy to announce the release of 'mini.input' - a module of 'mini.nvim' that makes asking for user input both more functional and visually pleasant. 'mini.nvim' now crossed two milestones: 45+ modules and 5000+ tests. Release blog post: nvim-mini.org/blog/2026-06...

nvim-mini.orgAnnouncing ‘mini.input’ – MINIGet user input with fully customizable key and view handling

4/6/26, 2:08 pm0 reposts15 likes

Nick

@nickjvandyke.bsky.social

4 June

Gratz! Looking forward to supporting this in opencode.nvim. The docs look promising 😀

Evgeni Chasnovski

@echasnovski.com

4 June

Thanks! To be fair, if a plugin can work within `vim.ui.input` API, it probably should. But when getting the input synchronously is a must, 'mini.input' is a good solution. Maybe `vim.ui.input` interface will cover synchronous case in the future (there are ways). We'll see.

Nick

@nickjvandyke.bsky.social

4 June

I use an in-process LSP to provide better completions for snacks.input, so I suspected mini.input also needs a bit of config to attach the LSP 🙂 Highlights is the other thing but from the docs, it seems the native vim.ui.input highlight option will just work!

Evgeni Chasnovski

@echasnovski.com

5 June

`vim.ui.input` interface supports custom completion with `'customlist,v:lua.my_compl'` completion field. Here `_G.my_compl` is a global function that takes data about base and has to synchronously return candidates. I'd suggest plugins to try and use this more universal approach.