You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be difficult to add an option to have fuzzy.Find() ignore spaces?
This would be nice to normalize the behavior with fzf.
For example, if I am searching through a bunch of filepaths, I will sometimes type part of one directory name, , and then a part of some other directory name or the filename.
In this sense, you are sort of passing in fragments to be matched, and the spaces are just being used to separate the fragments.
I saw that there was another similar issue requesting support to allow the order to be ignored, which is indeed how fzf operates, but even if the method still expects search phrases to be provided order, this would still be useful, imo.
Thanks for taking the time to put this library together and share it with the community! It works really well overall and was quite simple to pick up and use.
The text was updated successfully, but these errors were encountered:
Would it be difficult to add an option to have
fuzzy.Find()
ignore spaces?This would be nice to normalize the behavior with fzf.
For example, if I am searching through a bunch of filepaths, I will sometimes type part of one directory name, , and then a part of some other directory name or the filename.
In this sense, you are sort of passing in fragments to be matched, and the spaces are just being used to separate the fragments.
I saw that there was another similar issue requesting support to allow the order to be ignored, which is indeed how fzf operates, but even if the method still expects search phrases to be provided order, this would still be useful, imo.
Thanks for taking the time to put this library together and share it with the community! It works really well overall and was quite simple to pick up and use.
The text was updated successfully, but these errors were encountered: