Page 1 of 1

Why does loc:!"" search file system?

Posted: 12 Feb 2014 17:07
by LittleBiG
Why does this start a file system search? I would think it shows the files with not empty location (from tag.dat):

Code: Select all

loc:!""

Re: Why does loc:!"" search file system?

Posted: 12 Feb 2014 17:16
by TheQwerty
loc: isn't a recognized prefix as far as I am aware.

If you wanted to search based on an Extra Column of type location, you need to use the prefix for that column: ex4.

Re: Why does loc:!"" search file system?

Posted: 12 Feb 2014 18:48
by admin
Inverted searches always scan the whole system, not only tag.dat.

What you need is this:

Code: Select all

loc:?*

Re: Why does loc:!"" search file system?

Posted: 12 Feb 2014 19:00
by TheQwerty
admin wrote:Inverted searches always scan the whole system, not only tag.dat.

What you need is this:

Code: Select all

loc:?*
What does this search for?

Re: Why does loc:!"" search file system?

Posted: 12 Feb 2014 19:13
by admin
For the first column named "loc":

Code: Select all

    + Extra Tags: Now Find Files by Extra Tags also supports the localized and 
      case-insensitive column captions as field prefixes. When you have a column 
      called "Rating" then this term can be used to find all items with "Rating" 
      better than 2.
        rating: > 2

Re: Why does loc:!"" search file system?

Posted: 12 Feb 2014 19:19
by TheQwerty
Ah-ha!

I definitely missed that in the change log. :oops:
Though that explains why I wasn't getting any results when searching for "loc:".


EDIT: So can the ID parameter of ExtraTags() be made to also support this?

If omitted return the definitions for all ETs, one per line.
Else If 1-5 > ex1-ex5.
Else If "ex#" > ex#
Else first column with matching caption.

Re: Why does loc:!"" search file system?

Posted: 13 Feb 2014 10:54
by admin
TheQwerty wrote:EDIT: So can the ID parameter of ExtraTags() be made to also support this?

If omitted return the definitions for all ETs, one per line.
Else If 1-5 > ex1-ex5.
Else If "ex#" > ex#
Else first column with matching caption.
Makes sense.

Re: Why does loc:!"" search file system?

Posted: 18 Feb 2014 23:45
by nerdweed
I plan to use the Checkbox section in a bit varied way.

Most checked items would be used for a different purpose (stored in ?:\Folder1\Folder2\ and beneath this hierarchy)and often the checkbox column would be used as a selection store. Now, when I plan to use this checkbox column as a selection store, I won't be interested in the other items and vice versa.

"Checked" goto "*?:Check:1 /t" ; returns all checked items.

How can I ignore the other set of items

Re: Why does loc:!"" search file system?

Posted: 19 Feb 2014 00:33
by TheQwerty
nerdweed wrote:"Checked" goto "*?:Check:1 /t" ; returns all checked items.

How can I ignore the other set of items
The '*' before the question mark tells XY to search all locations if you omit it then XY will search the current path:

Code: Select all

"Checked in Current Path" goto '?:Check:1 /t';

Re: Why does loc:!"" search file system?

Posted: 19 Feb 2014 17:20
by nerdweed
Sorry, if I wasn't very clear. But this isn't what I was looking for is to find "Any checked item in the whole tags DB that can be scattered across the filesystem, but not that one particular folder and its subfolders.

Its like find all tagged items except those items where path like ?:\Folder1\Folder2

Re: Why does loc:!"" search file system?

Posted: 19 Feb 2014 17:53
by TheQwerty
I'm not sure if there is a better way to achieve this using quick name searches but this seems to work for me:

Code: Select all

"Check but not in ?:\Test\B" goto "*?:Check:1 & !prop:#<get propertyindex ""folder path"">:""?:\Test\B"" /t";
You need to replace "?:\Test\B" with the path you want to exclude.

You may also need to replace "folder path" with the correct name for the property - though you might just want to identify it by number and replace the entire '<get propertyindex ""folder path"">' with the property number, in my case 177.

Re: Why does loc:!"" search file system?

Posted: 19 Feb 2014 21:45
by nerdweed
Sadly, this is painfully slow. Getting property names of 100k files would certainly lead to this.

Current workaround, add a tag to these files and ignore that tag. Thanks for your help :)