I wouldn't have guessed that in a million years. My intuition simply told me that hello*world would match hello world and helloworld and hello1234world without having to type leading and trailing asterisks. because Everything normally treats whitespace as a logical AND. This is the way the mayority of Everything users intuitively think.void wrote:When using wildcards the entire filename is matched.
Please make sure you use a * prefix and * suffix if you want to find a wildcard expression anywhere in the filename.
Likewise, the ? wildcard only works if the users includes leading and trailing asterisks, which something I would had never guessed either:
gr?y should match both gray and grey, but it matches nothing unless you type *gr?y*
I can see how the current implementation might be useful in situations where you want the search string to match at the beginning or the end of the file path, but 99.9% of the time this is not the case, because we normally search a part of the file path, which means that typing the leading and trailing asterisks becomes an unreasonable requirement. For the rare cases where the search string must match at the beginning or the end of the file path, users may use RegEx's ^ and $. In other words, for the sake of ergonomics the task that's more likely to be done all the time should require the least amount of keystrokes and thinking.
I did a Google search for this "problem" and found quite a few users were also baffled by the way wildcards work in Everything, which probably means that this can be improved/simplified becasuse it doesn't work the way people expect it to.
By the way, thanks a million for all the recent bug fixes, Everything is working rather sweet!
