-
Notifications
You must be signed in to change notification settings - Fork 7
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
Conflict with nvim-notify
#24
Comments
Good morning and thank you for bringing this to attention! I am not familiar with In nvim-peekup/lua/nvim-peekup/peekup.lua Line 105 in e8ad8c7
I plan to re-factor the whole codebase and release a new version of this plugin once Neovim 0.1.0 ships, namely when a standard API for floating object is agreed upon and made more or less the standard (otherwise I will have to change it whenever a new 0.0.X release is published), and all plugins convert to that. Meanwhile coming back to your problem: could you try to fork this repository and create a version removing the |
Good morning @gennaro-tedesco , it seems we are in the same time zone. In my own understanding, and I'm not familiar with nvim-notify, it's just a dependency, This bug occurs when a peek window exists and then a notify window pops up. If no popup appears it works all good. It looks like it's because a popup appears to make |
So, if I understand correctly:
if this is the case (please correct my understanding if wrong) I would say this is due to the fact that |
Yes, that's what I meant. I think it's a problem with the neovim plugin ecology that there isn't a uniform and well established rule to prevent this from happening. I was just wondering if there was an easier way to fix it, like |
I share your sentiment that the current plugin ecology is not uniform. Recently there has been a similar discussion thread on reddit and as you can see from the comments, many people lament the conflicting defaults or plugins stopping working when others are invoked.
This is because until we reach a stable Neovim version 1.0.0, features and API rules are being changed constantly and people develop according to what is there at that point in time. I will have a look at the code of |
@YuCao16 I have released a new version of the plugin (see v0.1.0 ) where I have improved the behaviour of the window on lose focus and window change (in particular now the border follows the newest Neovim api, so it should be redrawn together with the window). Now at any window change the peekup window should close automatically and this should avoid any conflict with Please update the plugin ( |
Thank you very much for your efforts, I have tried the latest version and everything seems to be fine. But I can no longer reproduce the previous bugs because I have switched from coc to the built-in lsp. |
I will then close the issue. Feel free to open another one if new unexpected behaviours shall occur. |
Hi,
I hope someone is still maintaining this plugin. I found that


nvim-peekup
would conflict withnvim-notify
, as shown below:Because
nvim-notify
will create a popup window, and seemsnvim-peekup
redraw the content but not the border:I tried to fix by myself, but I'm just too unfamiliar with Lua, hope someone will help, thanks!
The text was updated successfully, but these errors were encountered: