multiple property search invalid since last update?

Discussion related to "Everything" 1.5 Alpha.
Post Reply
anmac1789
Posts: 669
Joined: Mon Aug 24, 2020 1:16 pm

multiple property search invalid since last update?

Post by anmac1789 »

To have multiple filename searches how come this doesn't work anymore ? filename:"abc";"123" but container-filenames:"123.txt";"cat.txt" works?
void
Developer
Posts: 16755
Joined: Fri Oct 16, 2009 11:31 pm

Re: multiple property search invalid since last update?

Post by void »

There is no filename: search function.

Please try:

name:"abc";"123"

name:
filelist: (did you mean filelist:?)
tuska
Posts: 1052
Joined: Thu Jul 13, 2017 9:14 am

Re: multiple property search invalid since last update?

Post by tuska »

void wrote: Sun Mar 03, 2024 11:53 pm There is no filename: search function.
viewtopic.php?p=48489#p48489
Search Functions:
filename: = match basename only (disables full path matching).

viewtopic.php?p=44828#p44828
Everything 1.5.0.1306 adds the following search functions:
filename:
anmac1789
Posts: 669
Joined: Mon Aug 24, 2020 1:16 pm

Re: multiple property search invalid since last update?

Post by anmac1789 »

tuska wrote: Mon Mar 04, 2024 5:58 pm
void wrote: Sun Mar 03, 2024 11:53 pm There is no filename: search function.
viewtopic.php?p=48489#p48489
Search Functions:
filename: = match basename only (disables full path matching).

viewtopic.php?p=44828#p44828
Everything 1.5.0.1306 adds the following search functions:
filename:
i understand the difference between filename: and file: but I wanted to know why multiple filenames can't be searched with ; (semicolon)
tuska
Posts: 1052
Joined: Thu Jul 13, 2017 9:14 am

Re: multiple property search invalid since last update?

Post by tuska »

2anmac1789
I interpreted this statement ("There is no filename: search function.") to mean that the search function filename:
does not exist and merely wanted to point out that there have been announcements about this search function.
anmac1789
Posts: 669
Joined: Mon Aug 24, 2020 1:16 pm

Re: multiple property search invalid since last update?

Post by anmac1789 »

tuska wrote: Mon Mar 04, 2024 6:20 pm 2anmac1789
I interpreted this statement ("There is no filename: search function.") to mean that the search function filename:
does not exist and merely wanted to point out that there have been announcements about this search function.
pardon me? I did not understand
void
Developer
Posts: 16755
Joined: Fri Oct 16, 2009 11:31 pm

Re: multiple property search invalid since last update?

Post by void »

i understand the difference between filename: and file: but I wanted to know why multiple filenames can't be searched with ; (semicolon)
There is no filename: search function.



filename: existed in some of the first Everything 1.5 builds.

filename: was replaced with name:
filename: is too ambiguous, in Windows it can mean the name part or the full path and name.

basename: is also an alias for name:
basename: can sometimes mean without extension (if specified).
However, basename: in Everything always includes the extension.
Use stem: if you want the name part without extension.



I've updated those links, thanks tuska.
anmac1789
Posts: 669
Joined: Mon Aug 24, 2020 1:16 pm

Re: multiple property search invalid since last update?

Post by anmac1789 »

void wrote: Mon Mar 04, 2024 10:02 pm
i understand the difference between filename: and file: but I wanted to know why multiple filenames can't be searched with ; (semicolon)
There is no filename: search function.



filename: existed in some of the first Everything 1.5 builds.

filename: was replaced with name:
filename: is too ambiguous, in Windows it can mean the name part or the full path and name.

basename: is also an alias for name:
basename: can sometimes mean without extension (if specified).
However, basename: in Everything always includes the extension.
Use stem: if you want the name part without extension.



I've updated those links, thanks tuska.
ok, so, seems like
stem:"name1";"name2";"name3"
and
name:"name1";"name2";"name3"
are working as intended
Post Reply