You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, message state is maintained by relying on Neovim message state (msg_clear).
It would be better to handle this by Noice using configurable timeouts.
This would make some of the code easier to work with and would fix some issues with messgages expiring before they have been displayed. (this can happen in async contexts like timers)
The text was updated successfully, but these errors were encountered:
folke
changed the title
Don't use Neovim state to determine if a message is cleared or still active
Don't use Neovim msg_clear to determine message state
Oct 29, 2022
folke
changed the title
Don't use Neovim msg_clear to determine message state
Don't use msg_clear to determine message state
Oct 29, 2022
Currently, message state is maintained by relying on Neovim message state (
msg_clear
).It would be better to handle this by Noice using configurable timeouts.
This would make some of the code easier to work with and would fix some issues with messgages expiring before they have been displayed. (this can happen in async contexts like timers)
The text was updated successfully, but these errors were encountered: