-
Notifications
You must be signed in to change notification settings - Fork 21
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
Yanky with sqlite enabled in combination with Noice locks up Neovim #56
Comments
|
The E656 error is because the yank is still in progress. Those are the errors I got from yanky. |
Found the issue. The bad query, cause an errro being displayed by Noice, while the yank is still in progress. Displaying that, raises the E656 error causing a loop. I'm working on a PR to fix this. Also better to save to history in |
Thanks for your feedback! Can you tell me what is your version of SQLite ? I try to fix it as soon as possible 🙂 |
I'm on Fedora 37. Probably becuase of missing https://www.sqlite.org/compile.html#enable_update_delete_limit indeed |
#57 will at least stop locking up Noice :) |
Thanks ! I merge this PR and I will fix this bad query ! |
Properly fixed by #58 |
Thanks for the fix, I'll try to improve error handling using |
@gbprod the problem with the error was caused by Noice, since we were inside a textlock, we did all message processing realtime. And that ttriggered the notify -> error coming in from |
I understand, thanks for reporting this error :) |
Hi!
First of all I really love what you did with Yanky. Awesome plugin!
I enabled the new
sqlite
storage earlier today and started having lock ups of Neovim pretty consistent.The lockup itself is caused by some sort of notifying -> triggers error -> tries to notify the error loop.
That part I can fix on my end, but the reason seems to be this error:
I get the lock ups when yanking or deleting lines. About 80% of the time.
It seems the usage of
sqlite
is causing this somehow. Any ideas?The text was updated successfully, but these errors were encountered: