-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
neovim-qt with Nvim v0.11.0 shows many "no notification handler registered" warnings #29363
Comments
#8053 |
After removing |
I have also been getting this behavior since upgrading to nvim 0.11 with ppa:neovim-ppa/unstable. For me, this is triggered by Shougo/deoplete.nvim and has prevented its usage since upgrading nvim.
on startup if I experience this issue with the following exact package pairs from the aforementioned PPA:
Despite the package names above containing the text "0.10.0", they do actually provide nvim 0.11. Uninstalling, removing the PPA, and downgrading to 0.10 with the |
This is because something is broadcasting an event via Nvim-qt should just not show that warning. For reference, this was indirectly caused by #28487 . I expected some issues like this, but so far only nvim-qt seems to be doing this kind of thing (complaining when it sees an unknown event). So I'm hoping that nvim-qt will change its behavior to quietly ignore unknown events. |
Problem
Those come every two seconds from the moment I open nvim . It comes in two flavors Dir and Gui errors.
Everything (i.e. the same profile) works well in nvim 0.10 .
Steps to reproduce
my neovim profile
Expected behavior
Works
Neovim version (nvim -v)
NVIM v0.11.0-dev-250+g61aabe073
Vim (not Nvim) behaves the same?
no idea
Operating system/version
Windows
Terminal name/version
nvim-qt
$TERM environment variable
unk
Installation
nightly
The text was updated successfully, but these errors were encountered: