One small inconvenience about kfind is that most of the times I need to always add * before and after my expression, as otherwise the program will think I’m trying to search for that exact file name.
I understand why it behaves like that, but it would be great if we could have an extra checkbox, maybe called [x] Search as substring or [x] Match anywhere in file name, that would implicitly add * before and after the expression.
What do you think?
I’ve also suggested (in another topic) to add Regular Expression search. I believe that for regexp functionality, this checkbox should be hidden/disabled, because with regexp there is ^ and $ for matching begin/end of string explicitly. (so the default should be to match anywhere, by design)
the search fields in kfind seem to behave differently depending on which field you are using
fields with a “*” can use wildcards to match characters and some regular expression syntax seems to be supported… for instance the search P[A-Z] vs P[a-z] return different results
fields without a “*” are verbatim searches matching only that exact string.
i’ve been playing with fzf all day yesterday, and finally got my .bashrc to where it needs to be for it function properly
the documentation/guide info i could find is all over the map with niche use cases and weird specifics that make it a real challenge to sort out…. someone really needs to write a proper guide for noobs.
but it’s working now and it does seem like a game changer for CLI jockeys, however i don’t (yet) see how it could be useful INSIDE of the kfind GUI.