luukvbaal

Repositioning turned out to be simpler, and seems more useful: #34269.

Hmm it seems `input()` is already distinguished as cmdline mode by `mode()`. Since `confirm()` and `input()` now use the same internal mechanism I think they should return the same mode....

OK so I'll change it to `one_key` prompts. Also changed it to avoid clearing number prompt messages, which aren't stored to be re-emitted.

Let's try it out on master for a while before backporting this to fix the regression. Keeping in mind that this fix will become redundant with a default extui, where...

My starting point (which I mentioned in https://github.com/neovim/neovim/issues/27811#issuecomment-1997091918, and is now present in the PR) is that _all_ messages go in a (disappearing) floating window. Only when they exceed some...

> Why shouldn't the default behavior continue to show the messages in the cmdline region? Because we can (with ext_messages and floating windows) easily choose a representation that makes more...

Thanks for reporting, I'm not too concerned with the second backtrace, which happens after the extui was already forcibly detached due to excessive errors. 'verbose' was not considered yet, good...

Yes, autocommands firing for the extui buffers/windows is probably unwanted, at least publicly (namespaced autocommands/editor objects(window buffer) could still be useful for the event handler itself). Perhaps avoiding that warrants...

See #31269 @przepompownia.

> I see that the example is not related to cmdline_block_* event. I think that is an oversight/bug. This pattern should emit `cmdline_block` events.