Beta-testing 'mini.input'

[echasnovski]

Please leave your feedback about new mini.input module here. Feel free to either add new comment or positively upvote existing one.

Some things I am interested to find out (obviously, besides bugs):

• Does it work well out of the box?
• Is configuration intuitive enough?
• Are default values of settings convenient for you?
• Is documentation and examples clear enough?

Thanks!

[231tr0n]

Thank you once again for the awesome module @echasnovski :) Just a nit pick, I donno if it is intended or not but in the readme file, a bold "Full Library" shows up which doesn't really make sense under the installation instruction.

[echasnovski]

... a bold "Full Library" shows up which doesn't really make sense under the installation instruction.

I think it does, as there are two ways the module is "packaged" as a part of full library and as a standalone repo. The first one is suggested, but the second one is possible. Also, as that file is used as a README in a standalone repo, it makes sense to mention and link 'mini.nvim' as a whole.

[231tr0n]

Ohh ok cool. I understand it now. It was not so obvious to me at first I should have read it again I guess. I taught it was a typo. One last ask, in the cmdline implementation with mini.input is it possible to include / and ? as well along with : in key mappings in the docs? Generally when I look for alternate commandline implementations, I want the cmdline to be in the center of the screen for everything. I believe most of them are the same as well.

[echasnovski]

... in the cmdline implementation with mini.input is it possible to include / and ? as well along with : in key mappings in the docs? Generally when I look for alternate commandline implementations, I want the cmdline to be in the center of the screen for everything. I believe most of them are the same as well.

Yes, it should be possible with some custom scripting. Important to note that Command line implementation is not the main goal of 'mini.input'. It will not handle well all possible scenarios (like command preview, for example). But its capabilities are enough for the basic Command line with completion and highlighting.

[drowning-cat]

Is there a Normal mode? In snacks.nvim#input, i_<Esc> switches to Normal mode, while n_<Esc> cancels the input, similar to CTRL-C. I can't imagine using a custom input without this feature.

[echasnovski]

Is there a Normal mode? In snacks.nvim#input, i_<Esc> switches to Normal mode, while n_<Esc> cancels the input, similar to CTRL-C. I can't imagine using a custom input without this feature.

The default key handler emulates Command-line mode. It is possible to script on top of it, but it won't be a part of 'mini.input'. Mostly because Normal mode felt too out of place in this type of "quick input" scenarios when I was using plugins that had it (like 'telescope.nvim'). I can imagine wanting to use it, but without it the input is fully usable.

[abeldekat]

I really like the new module!

In the help, :h MiniInput.config, there is a line that I don't understand:

It is also important to never change the current Neovim for |MiniInput.get()| to work as expected.

Is this about detach/attach?

Also, what is the intention of config.scope when the value is "project"?

[echasnovski]

In the help, :h MiniInput.config, there is a line that I don't understand:

It is also important to never change the current Neovim for |MiniInput.get()| to work as expected.

Is this about detach/attach?

It was meant to be "Neovim mode". I'll adjust this.

Also, what is the intention of config.scope when the value is "project"?

As with any other value, it is up to the one who initiated the input. In general, it is usually the answer to the question "The input for something related to the scope (cursor/line/.../editor/project)". It was added mostly to follow the upstream documentation of vim.ui.input (current master but planned to be part of 0.12.3).

[clukki]

Thank you for making this new module! I've waited so long for this to be able to entirely replace snacks.nvim with mini.nvim (lol). One thing that I would wish for is something similar to Ctrl-f in cmdline mode, which opens up a separate buffer for editing. But after looking at the implementation I'm not sure if that can be done...

[echasnovski]

One thing that I would wish for is something similar to Ctrl-f in cmdline mode, which opens up a separate buffer for editing. But after looking at the implementation I'm not sure if that can be done...

Yeah, I am afraid so. The very important point in 'mini.input' is that it does not change the mode and in the end returns the value. This is not quite possible (i.e. it might be done to a certain extent, but in a not very stable way) if input is taken through a regular buffer.