System files in temp excludes.

[harryray2]

Possibly add facility to add hide system files and/or folders to temp excludes?

[void]

I will consider an option to do this or an option to exclude indexed properties with a specific value.
Thank you for the suggestion.

You would need to index attributes to make this feasible.

[harryray2]

Thanks, excluding with specific values is a good idea.

I currently exclude system files with !attrib:s...how do I exclude multiple attrib on one search line without having to enter !attrib: for each attribute?

[void]

With group expansion:
!attrib:<r|h|s>
(which becomes !<attrib:r | attrib:h | attrib:s>)

Or with multiple !attrib: calls, for example:
!attrib:r !attrib:s !attrib:h

[ChrisM]

With group expansion:
!attrib:<r|h|s>
(which becomes !<attrib:r | attrib:h | attrib:s>)

Or with multiple !attrib: calls, for example:
!attrib:r !attrib:s !attrib:h

This took me quite a while to find, as I don't think it is mentioned in the Help files for 1.4 or 1.5a.
Is it possible to change this feature to operate the same as "attrib" does already?

For example, "attrib:sh" works just fine to show System and Hidden files. It seems entirely logical to me that "!attrib:sh" would hide System and Hidden files. That's how all of the other functions work when you add a ! or "no". (as far as I know)

[void]

To clarify,

attrib:sh

finds files that are both system and hidden.

!attrib:sh

does the exact opposite.
with

!attrib:sh

you may see results that are either system OR hidden, but never both.



To find files that are system OR hidden, search for:

attrib:s | attrib:h

-or-

attrib:<s|h>

To hide files that are either system OR hidden (or both), search for:

!<attrib:s | attrib:h>

-or-

!attrib:<s|h>

I'll add support for ; OR lists to make it easier to define an OR attribute list, eg: attrib:s;h

[ChrisM]

I see now, thank you for explaining and adding additional support for OR syntax.

If I may, I'd like to suggest a slight change to "attrib" wording in the Search Syntax help:

attrib: Search for files and folders where the attributes contains the all specified flags.

("the" is technically correct, but it only implies "all" instead of stating it clearly which I think helps)

[void]

attrib: Search for files and folders where the attributes contains the all specified flags.

Done for the next update.
Thanks for the suggestion.

[ChrisM]

Thanks!

I just noticed a typo in my post since "contains" is plural. So here would be the final text, so be clear:

Code: Select all

attrib: Search for files and folders where the attributes contain all specified flags.

Also, I don't think it's worth making a new thread for, but I wanted to mention that I don't see these features in the 1.5a Search Syntax Help yet (written by me in the style of the help file):

Code: Select all

Modifiers:
 distinct:	Matches files with up to 1 duplicate of given property (default: name)
 unique:	Matches files with no duplicates of given property (default: name)
 all-strings:	Match all strings instead of any. ("all-strings:author:jack;jill" = must contain jack AND jill)

Modifier Syntax:   (I would remove "wildcard" from the name since it's being expanded)
 modifier:<value1 value2>	Matches value1 AND value2
 modifier:<value1|value2>	Matches value1 OR value2
 modifier:value1;value2		Matches value1 OR value2 (Semicolons work as OR operators for number/dates/text. Escape them with ")
 ::modifier:value		Prefix a search modifier with :: to enable it Globally

sha256	(I don't know where it would go but it feels important to mention for the "dupe" and "distinct" modifers..)

Side note: Doesn't all-strings just convert ; to AND?
As in, all-strings:name:google;search performs identical to name:<google search>?

On second thought, after typing all that out.. I will probably make a new thread about the help file at some point.

[void]

The next alpha update will use:

attrib: Search for files and folders where the attributes include all the specified flags

distinct: Matches files without duplicates of given property (default: name)
all-strings: Match all strings instead of any. ("all-strings:author:jack;jill" = must contain jack AND jill)

I have put these on my TODO list.
(these functions where added after I wrote the syntax help)

Modifier Syntax: (I would remove "wildcard" from the name since it's being expanded)

the content wildcard: modifier behaves differently to filename wildcards.
filename wildcards only support * and ?
content wildcards support C escapes (\\), [] sets, # (any 0-9 digit), * and ?
(basically the same as visual studio wildcards)

modifier:<value1 value2> Matches value1 AND value2
modifier:<value1|value2> Matches value1 OR value2
modifier:value1;value2 Matches value1 OR value2 (Semicolons work as OR operators for number/dates/text. Escape them with ")

Modifiers support the < > style (not the ; style)
Only functions support the ; style

I will add the following under functions:

Code: Select all

function:<value1 value2>	Matches value1 AND value2
function:<value1|value2>	Matches value1 OR value2
function:value1;value2		Matches value1 OR value2

::modifier:value Prefix a search modifier with :: to enable it Globally

This was commented out because it initially didn't work on all modifiers.
It does now, so I will add it back in..

sha256 (I don't know where it would go but it feels important to mention for the "dupe" and "distinct" modifers..)

I will consider adding this to the examples.
Thank you for the suggestions.

Side note: Doesn't all-strings just convert ; to AND?
As in, all-strings:name:google;search performs identical to name:<google search>?

While it does change the meaning of ; to AND
All strings still need to match.

allstrings:abc;123 will not match abc;123;foo
because foo is not matched.

allstrings:foo;abc;123 will match abc;123;foo
(order is not important)

[ChrisM]

Thanks for all of that!

While it does change the meaning of ; to AND
All strings still need to match.

allstrings:abc;123 will not match abc;123;foo
because foo is not matched.

allstrings:foo;abc;123 will match abc;123;foo
(order is not important)

To clarify - I think my reason for mentioning this is that if the functionality is identical to AND, isn't "allstrings" a redundant modifier which can be removed to reduce complexity?

(it might not be if there is some other use-case for it that I don't know about)

[void]

allstrings: applies to multi-string values.
Name is not a multi-string value.
Tag is a multi-string value.

allstrings: is ignored with name: and other non-multi-string values.
allstrings: will only work on tag: and other multi-string values.

allstrings: use case example