-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vim.fn.inputlist
quirks
#112
Comments
I just pushed an update that doesn;t hide mini messages when the ui is blocking. I already did the same for nvim-notify. This probably fixes your issue. Can you test it? |
@folke |
Sorry to comment on a closed issue, but somewhat related to To be more clear: if I set specific options for formatting certain cmdline patterns (say like in the README) the prompts that display with input or confirm do not undergo the same behaviour (for instance they don't respect the highlight groups or titles that are set), thus I presume they need special format patterns to be included? |
For confirm, you can configure the Configure it with As for You can submit a feature request to Neovim for that :) |
Wait, I'm wrong, apparently |
@gennaro-tedesco just pushed an update that makes this configurable. Check the docs b645e30 Default config, adds |
Ooops, I see that |
@gennaro-tedesco input is fixed. See my previous comment :) |
Woow, you're faster than we can check :D Thank you for all the effort really. |
Firstly, apologies as I keep coming here with more issues and not fixes!
Is there a config option or perhaps making it a default behavior to always keep the prompt window open until choice for
vim.fn.inputlist
made or exited?With
orgmode
plugin which heavily usesinputlist
for a variety of functionality, from opening files to exporting pdfs, the popup view for choice stays on for a couple of seconds and disappears, like thisOn the other hand, I dont know if this is chiefly a problem of
inputlist
. I tried to reproduce with a simple example and it works as expectedLogs
Since this is not exactly an error, there are no logs
Noice config
The text was updated successfully, but these errors were encountered: