Closed rmagatti closed 3 years ago
yep good catch. Will address that as soon as possible. Thanks for reporting :)
This should be implemented in the last commit. Feel free to reopen if it doesn't work as expected (and feel free to open new issues if you find more oddness. I know its not perfect yet :rofl:).
Thanks for reporting :)
Description
So I know the readme mentions there won't necessarily be 1:1 feature parity with fzf, but I did notice something strange when using fzf-native that's quite different than fzf that I'm not sure is the intended behaviour.
When starting the match with a !bang exclusion pattern, in fzf results still show up, respecting the exclusion match, with fzf-native they don't.
Examples
Correct exclusion when !bang pattern is not the first pattern to match
Example of no results showing when the !bang match is the first match, but appearing when extra matching is provided.
Fzf/expected behaviour