Open MarkuBu opened 3 years ago
To summarize: Though the matching algorithm of skim
, for each line piped to it, prioritizes matches at the beginning of each token (separated by slashes /
, say), among the search string tokens (separated by blanks) it prioritizes the first token only, not the following ones.
This is in contrast to fzf
and peco
, but seems similar to fzy
.
If I compare skim and fzf I see amajor differences. If I enter a search pattern fzf finds what I expect, skim does not
For example: I have the nerd-fonts in my Downloads folder. Inside is a package.json file. If I run fzf with no arguments and enter "dow ne pa" I have a perfect hit. If I do the same in skim I'm not even close to a hit
Another example: I have a clone of QMK with my own layout named PUQ for the atreus42. If I enter "atre key puq" in fzf the first highlighted file is the keymap.c. The same pattern in skim highlights a file that doesn't even contain "key"