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
Hi there!
I've found that if there is active notification popup, created by nvim-notify, and I call Sayonara, it (Sayonara) just quits nvim as if there was no opened buffers.
I previously reported that to nvim-notify (here is a link o the issue: rcarriga/nvim-notify#147 ), and I wrote there that I think it can be related to unlisted buffers that popup creates, but I'm not sure.
At #1 I just pressing "q" which is mapped to <cmd>Sayonara<CR>, and Sayonara closes buffers (as expected).
At #2 I firstly call notify to create a notification pupup, and then call Sayonara and it closes the whole nvim instance instead of just current active buffer...
The text was updated successfully, but these errors were encountered:
Hi there!
I've found that if there is active notification popup, created by
nvim-notify
, and I call Sayonara, it (Sayonara) just quits nvim as if there was no opened buffers.I previously reported that to
nvim-notify
(here is a link o the issue: rcarriga/nvim-notify#147 ), and I wrote there that I think it can be related to unlisted buffers that popup creates, but I'm not sure.And here is a asciinema recording showing the issue: https://asciinema.org/a/YhWFoYswb9CebKwtnRfOhEu4e
At
#1
I just pressing "q" which is mapped to<cmd>Sayonara<CR>
, and Sayonara closes buffers (as expected).At
#2
I firstly callnotify
to create a notification pupup, and then callSayonara
and it closes the whole nvim instance instead of just current active buffer...The text was updated successfully, but these errors were encountered: