I like using the folder path quick-search ability, such as "\AppData". However, sometimes I only know that part of a word is in the folder name, so I try to do a wildcard folder path, like "\*cache*" (if I'm looking for files in folders that have "cache" in their name. But when trying to use a wildcard in that case, it will only show files in folders with something preceding "cache" in the folder name, expecting something must be there.
Is there a way to make a wildcard optional without having to disable the "Match whole filename when using wildcards" option?
Thanks!
Possible to do potential-wildcard-but-maybe-not in folder paths?
-
- Posts: 79
- Joined: Sun Jul 13, 2014 12:20 am
Re: Possible to do potential-wildcard-but-maybe-not in folder paths?
There is a setting: Match whole filename when using wildcards that is enabled by default.
That will "cause" \*cache to be seen as the whole file/folder name, meaning that the name ends with cache.
To get names with cache in their names, you can use \*cache* or disable aforementioned setting.
It can be found under Menu:Tools > Options > Search.
That will "cause" \*cache to be seen as the whole file/folder name, meaning that the name ends with cache.
To get names with cache in their names, you can use \*cache* or disable aforementioned setting.
It can be found under Menu:Tools > Options > Search.