Make ivy--flx-sort more intelligent #843
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 makes flx sorting much more enjoyable for me. |
|
Thanks! |
raxod502
added a commit
to radian-software/radian
that referenced
this pull request
Dec 29, 2016
The code referenced as a potential future solution has now been merged into ivy upstream [1]. [1]: abo-abo/swiper#843
This was referenced Jan 19, 2017
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.
This improves the behavior of
ivy--flx-sort. In particular, the following has been changed:flx-scoreis not called on candidates that do not match the given input. (And the fuzzy matching is done in an optimized fashion.)ivy-flx-limitthe firstivy-flx-limitcandidates by length are still scored and sorted, which can often lead to quality results, even with large numbers of candidates and small inputs.flx-scoreties are broken by length (shorter wins)