Results seem to be in reverse order #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR will expose the #15 to all users... maybe we can wait to fix the issue before merge this? What do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The search results seem to be in the reverse order
You can see that the results are more accurate in the second screenshot
The only downside to this is that the first entry will be a
nilbecause of some bug that I will create a issue on later (it's present in all ivy-youtube versions, but it's normally pretty well hidden at the bottom).This is identical on pretty much every version of
ivy-youtube(initial commit, before my recent changes, master)I'm using
emacs -qhereBefore reversing order
After reversing order
I will admit that the solution is kind of hacky though hah