Open heygarrett opened 1 year ago
I think nvim-notify's default implementation should be improved in a way that if vim is in [the fast event](https://neovim.io/doc/user/lua.html#vim.in_fast_event()), it should defer the execution.
A workaround would be:
-vim.notify = require("notify")
+vim.notify = vim.schedule_wrap(require("notify"))
BTW it may have some unwanted consequence, e.g., the ordering of async events can be slightly different than the invocation was made, due to vim.schedule
.
When triggering omnicompletion with a language server that doesn't support completion a helpful message is displayed:
But when nvim-notify is installed it causes an error instead:
Minimal repro.lua config:
Steps to reproduce:
nvim -u repro.lua config.fish
(I'm using a fish file)<c-x><c-o>
Expected behavior:
The helpful LSP message would be displayed
Actual behavior:
Error
Additional info:
NVIM v0.9.1 Build type: Release LuaJIT 2.1.0-beta3
system vimrc file: "$VIM/sysinit.vim" fall-back for $VIM: "/opt/homebrew/Cellar/neovim/0.9.1/share/nvim"
Run :checkhealth for more info