Improve matching of CharSelect

[al1-ce]

Is your feature request related to a problem? Please describe.
When I'm trying to get unicode characters it's extremely frustrating that results are completely unrelated to search. Example:

On top is kitten unicode-input, on bottom wezterm's CharSelect. Top results are fairly close to what I need (and to be honest look way better), bottom are absolutely not what I want to find

Describe the solution you'd like
Fuzzy search instead of what it's right now

Describe alternatives you've considered
Using kitty's char select which doesn't work with wezterm, i.e can't select characters or backspace to delete typed term

[wez]

FWIW, the results you are seeing right now are fuzzy matches, produced by https://crates.io/crates/fuzzy-matcher
It just so happens that line is fuzzy matching closer to linux than low line with its algorithm.

[al1-ce]

Strange, it should matching line related things first instead of linux then...

Maybe it's worth implementing something like https://dlang.org/library/std/numeric/gap_weighted_similarity_normalized.html ? In my experience it does very good matching.

[bew]

Maybe we could replace the use of the fuzzy-matcher crate with nucleo, which is both much faster and uses the same scoring system as fzf 🤔

[al1-ce]

Imo nucleo looks good and if they're right about similar matching to fzf it'd certainly be better choice

[wez]

FWIW, I did a quick test with the nucleo-matcher and I'm not convinced this is what you want either:

[al1-ce]

Tbh looks better then before

What if to trick it by adding spaces before and after input string? Should probably trick matcher..?

I would've tested some things myself (namely trying to implement gap weight similarity algorithm), but I'm very unfamiliar with rust and didn't really liked it when I tried

[wez]

I've switched this to nucleo in main. I have low interest in trying to actively game the algorithm. I think that matching linear... before low line is totally reasonable in this situation.

Note that once you select low line once, it will appear in the recent list making it quicker to reuse again.

[al1-ce]

That is fair, it's way better then it was before and personally I'm ok with that, so, close when ready

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.