Rocco V
16 discussion posts
The title says it all. I was using 3.2 Beta 2 and it completely ignores the 'Exclude Path(s)" option. The stable version 3.1.4 works ok.
Rocco V
16 discussion posts
I'll keep an eye out for it. Oh, it's already updated. Cool. Thanks.
Jun 13, 2014 (modified Jun 13, 2014)
•
#3
Rocco V
16 discussion posts
I am now using beta 3 but Exclude Path(s) doesn't seem to work the way I would expect it to. Let me try to set up a scenario.
Say you have the following folders
C:\Program Files\app1\folder1\folder2
If I'm in app1and want to exclude folder1I can add "folder1" to the Exclude Path(s) option and it works as expected.
It seems to me though, if I'm in folder2 I should still be able to search it even though "folder1" is still in the Exclude Path(s) option because there is no "folder1" in folder2. But what happens is it will search folder2but none of it's sub folders.
It seems to me that Exclude Path(s) should only apply to folders below the current folder. As it is now if the current folder includes an excluded path it should theoretically always return no results so I can't see the point of it.
I hope I'm clear enough.
Makes sense! That is a bug, as it should return no results since folder1 is in all of the paths to the stuff in folder2 and below. We've fixed that up for 3.2 which we released yesterday. Your suggestion was interesting, but it would make the searching much slower, as it's not matched on a folder by folder basis, but rather the entire path to the file that it's checking against.
Rocco V
16 discussion posts
Speed is important, so fair enough. It's not that big a deal anyway because it's easy enough to just select the Exclude Path(s), with "folder1" added, from the drop down menu when I want to search the "app1" folder. Then when I want to search folder2 again I just switch back. No typing necessary (after the first time of course).
