-
Notifications
You must be signed in to change notification settings - Fork 28
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
Closing Yazi while renaming causes the "Invalid buffer id" error #594
Comments
Nice catch, I don't think I have seen this myself. I'll add that check and let's see if it can be avoided 👍🏻 |
By the way, I think it's possible to configure noice.nvim to have the popups displayed at the bottom right instead of the top right. I had this setting before https://github.com/folke/snacks.nvim was added to lazyvim (which I use). That changed the way it should be done. It looks like without snacks.nvim I did it like this, and right now (with snacks.nvim) I do it like this If you like the idea, it might reduce the amount of annoying messages that cover your work 🙂 |
Cool, definitely check it out, and thanks for the fix! |
I occasionally get this error:
It's not always reproducible and only happens when I quickly close Yazi and go back to nvim after triggering a rename.
Since I use noice.nvim, it appears in the top right corner of the UI, blocking part of the content, which is a bit annoying.
I think a simple fix would be to check if the buffer ID is still valid using
nvim_buf_is_valid
before callingvim.api.nvim_buf_call
, just in case. It's more like a safety check and wouldn't break anything existing.The text was updated successfully, but these errors were encountered: