file: including path
-
- Posts: 5
- Joined: Fri Aug 19, 2016 4:26 pm
file: including path
Tried to figure out what I'm doing wrong but when I search using the file: modifier, the results include text files where the search term is in the path. For example...
file: (unsorted) .txt
Lists all .txt files where (unsorted) is part of the path or part of the filename.
I started using the current Beta Version 1.4.0.713b (x64) with Windows 7. Recently did a clean install of Windows 10 and it still does the same thing.
Thanks
file: (unsorted) .txt
Lists all .txt files where (unsorted) is part of the path or part of the filename.
I started using the current Beta Version 1.4.0.713b (x64) with Windows 7. Recently did a clean install of Windows 10 and it still does the same thing.
Thanks
Re: file: including path
You also have Search | Match Path enabled.
-
- Posts: 5
- Joined: Fri Aug 19, 2016 4:26 pm
Re: file: including path
Thanks but I unchecked Match Path and it still does the same thing. However, I suspected it wouldn't fix the problem because that setting reads "Match Path when a search term contains a path separator" and I'm not using a path separator in my search.therube wrote:You also have Search | Match Path enabled.
I experimented and whether I check or uncheck that setting, use a path separator or not, I get the exact same results.
Re: file: including path
Is there anything displayed in the status bar to the right? eg: PATH? REGEX?
Are there any settings checked in the Search menu?
Have you overwritten the file: search with your own filter macro?
Could you please send the verbose debug output after performing a file: (unsorted) .txt search?
To run Everything in verbose debug mode:
Are there any settings checked in the Search menu?
Have you overwritten the file: search with your own filter macro?
Could you please send the verbose debug output after performing a file: (unsorted) .txt search?
To run Everything in verbose debug mode:
- Completely exit Everything (Right click the Everything system tray icon and click Exit)
- From a command prompt or shortcut, run Everything.exe with the -debug -verbose command line options:
Everything.exe -debug -verbose
-
- Posts: 5
- Joined: Fri Aug 19, 2016 4:26 pm
Re: file: including path
void wrote:Is there anything displayed in the status bar to the right? eg: PATH? REGEX?
Are there any settings checked in the Search menu?
Have you overwritten the file: search with your own filter macro?
Could you please send the verbose debug output after performing a file: (unsorted) .txt search?
To run Everything in verbose debug mode:
- Completely exit Everything (Right click the Everything system tray icon and click Exit)
- From a command prompt or shortcut, run Everything.exe with the -debug -verbose command line options:
Everything.exe -debug -verbose
Sorry for the delay getting back to you but I only use Everything periodically and wanted to think about this for a while. It looks like my confusion has to do with two different settings...
Menu > Search > Match Path
Options > Search > Match path when a search term contains a path separator.
When I toggle the one under Menu > Search, it seems to work fine.
In my prior post, when I said "but I unchecked Match Path and it still does the same thing", I was referring to one under Options > Search
So it looks like my issue has to do with Options > Search > Match path when a search term "contains a path separator".
Maybe I shouldn't have taken it literally? But it seemed quicker to add a simple path separator (\) within my search terms, than to change the setting under Menu > Search > Match Path
So after playing around more, it looks like just adding a path separator doesn't doing anything, and I also need to add at least part of a path?
Re: file: including path
The match path modifier is applied to a "Search term" if that "Search term" has a path separator (\).So after playing around more, it looks like just adding a path separator doesn't doing anything, and I also need to add at least part of a path?
A search term in Everything is a word or phrase. Search terms are separated by spaces, | or other search operator.
Examples of a search term in Everything:
\downloads
"c:\program files\"
settings\
system32\drivers\etc
*.mp3
The search: my \ downloads is made up of 3 search terms: my AND \ AND downloads, only the single \ will have the match path modified applied, which is not what you want. Please make sure that the path separator (\) is a part of the search term for the best results.
Another example, which may make this easier to understand, the search: \downloads foo.mkv is two search terms, \downloads AND foo.mkv , only \downloads will match paths (because it contains a \), whereas foo.mkv will not match paths.
-
- Posts: 5
- Joined: Fri Aug 19, 2016 4:26 pm
Re: file: including path
Thanks for the response and I'll give the above a try over the next few days to see what I think. If I have any issues I'll post back here, but I think I understand. Thanks for your time.void wrote:The match path modifier is applied to a "Search term" if that "Search term" has a path separator (\).So after playing around more, it looks like just adding a path separator doesn't doing anything, and I also need to add at least part of a path?
A search term in Everything is a word or phrase. Search terms are separated by spaces, | or other search operator.
Examples of a search term in Everything:
\downloads
"c:\program files\"
settings\
system32\drivers\etc
*.mp3
The search: my \ downloads is made up of 3 search terms: my AND \ AND downloads, only the single \ will have the match path modified applied, which is not what you want. Please make sure that the path separator (\) is a part of the search term for the best results.
Another example, which may make this easier to understand, the search: \downloads foo.mkv is two search terms, \downloads AND foo.mkv , only \downloads will match paths (because it contains a \), whereas foo.mkv will not match paths.
Re: file: including path
void wrote:
Another example, which may make this easier to understand, the search: \downloads foo.mkv is two search terms, \downloads AND foo.mkv , only \downloads will match paths (because it contains a \), whereas foo.mkv will not match paths.
Just to understand the search syntax better:
\downloads (or path:downloads) will also match files such as c:\bar\xxdownloadsyy.foo. Is that the way it is supposed to work?
Additionally, only with Recycle.bin in the exclude list, if I delete folder bar and then restore it, c:\bar\xxdownloadsyy.foo does not show in the result list until a rebuild.
Re: file: including path
What version of Everything?
You might be running into, http://www.voidtools.com/forum/viewtopi ... 418#p15418.
You might be running into, http://www.voidtools.com/forum/viewtopi ... 418#p15418.
Re: file: including path
Tried both 1.4.0.713b & 1.4.1.727b. Same results either way.therube wrote:What version of Everything?
You might be running into, http://www.voidtools.com/forum/viewtopi ... 418#p15418.
Re: file: including path
\downloads will match files or folders inside a folder starting with \downloads, eg:Just to understand the search syntax better:
\downloads (or path:downloads) will also match files such as c:\bar\xxdownloadsyy.foo. Is that the way it is supposed to work?
c:\downloads\foo.txt would match.
\downloads will also match files starting with \downloads which might not be what you want.
c:\somefolder\downloads.txt would match.
searching for downloads\ would always return results inside a folder that ends with downloads.
c:\downloads\foo.txt would match.
c:\somefolder\downloads.txt would not match.
path:downloads will search for downloads in the full path and filename.
c:\downloads\foo.txt would match.
c:\somefolder\downloads.txt would match.
This is a limitation of Everything, subfolders and files inside an excluded folder that is moved so it is included will not be added to the index.Additionally, only with Recycle.bin in the exclude list, if I delete folder bar and then restore it, c:\bar\xxdownloadsyy.foo does not show in the result list until a rebuild.
Only the folder bar would be added, since the subfolders and files are unknown to Everything.