-
Notifications
You must be signed in to change notification settings - Fork 16
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
Recent change seems to break wilder.nvim #24
Comments
My bad. I've reverted the changes for now. Thanks for the report. |
i think maybe it should be wilder to update it code? |
This change is not supposed to be breaking, we're only moving files around in an API-compatible way. |
Sorry for the late reply @romgrk , I got quite busy yesterday didn't get a chance to look into things.
I totally get what you mean, and, honestly, I was confused myself Hopefully today, when I get a chance, I'll try to see what that |
Hey @romgrk , so I tried to see what the I'm getting QUITE a few ones since I think But, this is what I see with the refactored code: { { "!", {} }, { "#", {} }, { "&", {} }, ... } And this is what I get with the old non-refactored code (or the reverted code): { { "!", {}, -inf }, { "#", {}, -inf }, { "&", {}, -inf }, ... } Hopefully, this gives a clue. Let me know if you need any other information that can help |
Hi, I'm using wilder.nvim, and it depends on this plugin for its fuzzy search.
After the recent change, I'm getting an error for this line saying that:
I'd appreciate if you let me know if there's a fix for this
The text was updated successfully, but these errors were encountered: