searching tags, semicolon seems to act as "or"

[abr01]

In your examples, you have tags:nature;illustration. I have tried my own version, but instead of getting AND results, i get OR. What would be the correct syntax to search for multiple keywords in the tags, or for that matter, in other search modes?

[therube]

OR is expected (& is what it says).
tag:nature OR tag:illustration

Does tag:nature tab:illustration work?
That would be an AND (though I'm not familiar with tag:).

[abr01]

It works halfways, from a quick test. With your syntax i find snow and bird, but also just snow (where snow was the first search item in the line, if that matters). So all results contain snow, but not always birds (these are only two example search strings, but i'd expect it for other cases to be similar).

I also did a test only searching for snow, whicht brought up about three times as many results, as for the combined example.

tags:snow tags:birds

[void]

Everything does a partial tag search.

Another search option:

tags:<snow birds>



Matches should be highlighted under the tag column.
What is shown in the tag column where only snow matches?



If you know the tag order, the following will work:

tags:"snow;birds"

Double quotes (") will match the ;



Please try the following search to match whole tags:

whole:multistring:tags:snow whole:multistring:tags:birds

-or-

whole:multistring:tags:<snow birds>

[abr01]

Didn't test them all yet, but the whole:multistring:tags:snow whole:multistring:tags:birds type of search works fine. I'm gonna test the other ones too.

Thanks guys!


/

What is shown in the tag column where only snow matches?

Looks like only the second search keyword was respected. Anyway, i can work with the multistring one.

[void]

Everything 1.5.0.1359a removes the need for multistring:

Everything will now automatically use multistring: on properties that have multiple values.



The following will now work as expected:

whole:tags:snow whole:tags:birds

-or-

whole:tags:<snow birds>

multi-string:

[abr01]

After some testing, this format turned out to be the only reliable one. The second example, whole:tags:<snow birds> doesn't work for me for some reason. But is there any way to simplify the input process, without having to type the lengthy whole:tags: part twice? I'm planning to build some multistring Everything search button in Opus, where i couldn't get the mentioned code to work yet.

whole:tags:birds whole:tags:snow

[void]

Thank you for the bringing this issue to my attention abr01,

Sorry, I have broken:

whole:tags:<snow birds>

with the latest Everything 1.5.0.1359a.



Everything is trying to find snow AND birds in each substring.

The next alpha update will search for a snow substring AND a birds substring.



For now, please use:

whole:tags:birds whole:tags:snow

[err_24546]

@abr01 a bit offtopic, but are you talking about Tags created with Directory Opus? Can you see that data inside Everything correctly? I remember that I could do it with Dopus v12, but if I create new ones or modify them with v13, they are no longer visible in Everything.

[void]

Everything 1.5.0.1360a fixes an issue with subexpressions and multistring properties.

The following will now work as expected:

whole:tags:<snow birds>

[abr01]

Thanks, that works. Would it be possible to change the behavior, so that no < > are even required, for convenience?

@err_24546, yes, i was referring mainly to those tags in Opus 12/13. Sorry, i missed this notification, just found it today. As ist seems, there was some progress already in version 1.5.0.1364a, so things might work again. I hope, that the abilities of Everything and Opus will converge, making it an even more brilliant combination of software. By that i mean, that using ET within Opus, regarding syntax details, is still a bit different. Anyway, i am doing lots of searches, and ET is enhancing Opus' own searching tools, which are also very powerful on their own.

[void]

Please try creating a filter to search the whole filename OR whole tags:

• In Everything, from the Search menu, click Add to filters....
• Set the Name to:
  Whole Filename or Whole Tag
• Change the Search to:
  #replaceterms:#(:$param:#):,#(:<whole:#term:|whole:tag:#term:>#):
• Click OK.

Filters can be activated from the Search menu, Filter bar (View -> Filters), right clicking the status bar, filter macro or filter keyboard shortcut.



Now you only need to search for:

snow birds

[abr01]

Please try creating a filter to search the whole filename OR whole tags:

• In Everything, from the Search menu, click Add to filters....
• Set the Name to:
  Whole Filename or Whole Tag
• Change the Search to:
  #replaceterms:#(:$param:#):,#(:<whole:#term:|whole:tag:#term:>#):
• Click OK.

Filters can be activated from the Search menu, Filter bar (View -> Filters), right clicking the status bar, filter macro or filter keyboard shortcut.



Now you only need to search for:

snow birds

It works! Even very quick, like instantly. Thanks!

Edit: is there a way to include this type of search into the Opus global search using Everything? How could i tell Opus to use the "whole tag" filter? Or, if this is still in the make, how to send the findings list to an Opus collection? Something along those lines.