Everything v1.5.0 Build 1301a Alpha [64-bit] appears to break search command

[SuperDude]

I use the following command to search for all copies of a specific file (the search is activated via a hotkey):

Everything64.exe -s nopath:exact:#quote:#[basename:"%1"#]:

Example: If I want to find all copies of just Bookmarks-1.5a.csv, I click on the file in Directory Opus, then activate my hotkey to make Everything search for that file. Everything Build 1301a shows this result (in the Search Edit field):

nopath:exact:"#[basename:D:\Everything64\BOOKMARKS-1.5a.CSV#]:"

NOTE: Only the Search Edit field is populated, there are no entries in the Result List. I also exited out of Everything, stopped the Everything Service, deleted the Everything-1.5a.db database, restarted the Everything Service, then restarted Everything. I waited for Everything to completely index all Properties, Content, etc, but get the same result.

[horst.epp]

Confirmed
Here the following example worked before:
nopath:exact:"#[basename:Everything.ini#]:"
Now no results are found.
With version 1300a all is fine again.

[void]

Thanks for the bug report SuperDude and confirmation horst.epp,

1301a changes some preprocessor search function names.

basename is now getbasename:


Sorry for the inconvenience .
This change was made to avoid a conflict with the basename property of a result.
I will look into reverting this change and possibly using $basename: syntax for result properties.



#get-basename:

[void]

Everything 1.5.0.1302a reverts the preprocessor changes in 1301a.

#getbasename: is now #basename: again.



The preprocessor will now expand in order:
User defines.
Preprocessor functions.
Character entities.
Literal runs.
Properties.

(instead of expanding properties first)



Everything will now accept $property-name: (as well as #property-name:)

This means:
#year: will now mean the preprocessor year function, not the year property.
Use $year: for the year property.



In short, the preprocessor syntax is now:
#function-name:
$property-name: