Hi,
I was exercising the column/property comparison;
stem:==ext: works well, it brings the filenames that have the same extension as their stem (filename w/o extension). example "sys.sys"
However ext:==stem: gives zero results. I'd expect it to give the same results as above.
Is there a reason for that? or is it a bug?
Regards, Skier.
Compare Column/Property
Re: Compare Column/Property
ext: isn't just a column property, but a special verb that also accepts semicolon-delimited input.
@void: The following information should be correct, but is not, and so I think there is a bug.
For the correct column property name, right click upon the column and select 'Search for Extension' from the menu.
This will reveal the correct name is extension:.
Examples:
works. ext:mp4;mkv
doesnt. extension:mp4;mkv
works. stem:==ext:
doesnt. ext:==stem:
extension:==stem: (should work, but instead it only returns extensions that contain two literal equal signs.)
stem:==extension: (should work, but instead it only returns stems that contain two literal equal signs.)
@void: The following information should be correct, but is not, and so I think there is a bug.
For the correct column property name, right click upon the column and select 'Search for Extension' from the menu.
This will reveal the correct name is extension:.
Examples:
works. ext:mp4;mkv
doesnt. extension:mp4;mkv
works. stem:==ext:
doesnt. ext:==stem:
extension:==stem: (should work, but instead it only returns extensions that contain two literal equal signs.)
stem:==extension: (should work, but instead it only returns stems that contain two literal equal signs.)
Re: Compare Column/Property
Thank you for the bug report Skier,
The Everything Preprocessor is being too aggressive.
The Preprocessor is trying to expand stem: and extension:, both will expand to nothing in this case.
I will tone down the Preprocessor in the next alpha update:
This change will only parse preprocessor text at the start of a term, for example:
include:mysearch.txt
clipboard:
shell:desktop\misc
To use the preprocessor anywhere in the term, use [function:args], for example:
pre[clipboard:]
property-name-1:==property-name-2:
Everything will lookup the property by name.
There are many property aliases.
ext is the same as extension.
While ext: is a search function, search functions are completely ignored when using property-name-1:==property-name-2:
The Everything Preprocessor is being too aggressive.
The Preprocessor is trying to expand stem: and extension:, both will expand to nothing in this case.
I will tone down the Preprocessor in the next alpha update:
This change will only parse preprocessor text at the start of a term, for example:
include:mysearch.txt
clipboard:
shell:desktop\misc
To use the preprocessor anywhere in the term, use [function:args], for example:
pre[clipboard:]
When using the search syntax:ext: isn't just a column property, but a special verb that also accepts semicolon-delimited input.
property-name-1:==property-name-2:
Everything will lookup the property by name.
There are many property aliases.
ext is the same as extension.
While ext: is a search function, search functions are completely ignored when using property-name-1:==property-name-2:
Re: Compare Column/Property
Everything 1.5.0.1311a will now only expand preprocessor functions with the function:arguments syntax at the start of the search term.
The following should now work as expected:
extension:==stem:
stem:==extension:
ext:==stem:
stem:==ext:
The following should now work as expected:
extension:==stem:
stem:==extension:
ext:==stem:
stem:==ext:
Re: Compare Column/Property
Thnx void,
You're wonderful.
You're wonderful.