client: For filtering, prioritize exact, startsWith #438
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.
In short
Rationale
It seems more likely to search for a channel/nickname with the starting letters rather than filtering by the middle, as that's how the channel/nickname list is sorted (when alphabetical sorting is enabled). Similarly, an exact match should emphasize that over any substring matches.
Quassel should prioritize results that exactly match, then start with, over the rest of the results that merely contain the filter string.
This is personal opinion, feel free to disagree!
Examples
Setup
acar
,bcar
,car
,careful
,caring
,racecar
/query [name]
car
car
with buffer filter, e.g. Ctrl+SBefore
After