Having to confirm twice on operation cancel

[kkharji]

Description

This is annoying a bit. the second line printed makes the prompt stay there instead of just be printed in console.

maybe differing results would make sense and solve this?

Neovim version

NVIM v0.6.1

Operating system and version

macOs

Steps to reproduce

1. create/rename/delete
2. cancel or confirm
3. console await user input

Expected behavior

after confirming or canceling action the focus should be back on the browser

Actual behavior

Await additional input.

Minimal config

..

[fdschmidt93]

Yeah, I've realized that commandline interaction & printing is not perfect. I'd hope that this would be resolved by switching towards notifications?

#72

I have to setup notifications and take a look at that PR.

[kkharji]

I guess it would be a by product of #72.

[jamestrew]

Unfortunately #72 doesn't solve this Press ENTER or type command to continue issue.

I'll look into it a bit more within the next couple of days. All I know is that stacking too many multline vim.notify or print beyond the cmdheight is the culprit. I'm not super sure how to force clear what's in the command bar besides throwing a vim.api.nvim_command('norm :esc<CR>') between the vim.notifys which feels very janky and dumb.

[kkharji]

Hmmm maybe then no new lines? flat text

[fdschmidt93]

So I've been cleaning up my dots a bit and also finally got around to installing nvim-notify and playing with that a bit.

I'll probably take over #72 eventually with my own PR (though borrowing some ideas :), from what I can tell there's two-three options here:

• swapping vim.notify with nvim-notify
• increasing cmdheight intermittently (a bit messy)
• Put messages into 1 line (as will my refactor) and then vim.cmd [[ redraw! ]] seems to work such that the 1 line solely remains in cmdline

As I understand it, hit-enter prompt is essentially triggering the redraw as it's otherwise not clear for (n)vim how to handle intermediate excess cmdheight.

[fdschmidt93]

This should hopefully be addressed now, so closing :)

Please let me know otherwise.