Everything 1.5 Alpha • Re: .metadata.efu Specification

Thank you for your reply.
The fog is clearing a bit more than before.

Filenames MUST be relative to the .metadata.efu file.

The efu files exported in step 1 above contain the full path in the Filename field, so I added the following step.
- 1.5) Edit all filename fields in the exported .efu files to contain only the filename.
I also pressed F5 just before pressing Ctrl+F5 in step 5.
However, the result of the query is-metadata-efu-property: is empty...

So, I tried including .efu files in the index, and after rebuilding the index, the files included in the .efu file created in step 1 appeared in the result of is-metadata-efu-property: !! Yes!!
In conclusion, even if metadata_efu: true is set, it doesn't actually work if .efu files are excluded from indexing.
Looking back at the explanation on this topic, I realize that you already made it clear...

Everything will lookup .metadata.efu files from your index.

The fog has almost cleared. Thanks for bearing with me.


I think the property definition override feature, including this one, will be a highlight feature of Everything 1.5.
Currently, manual operation (Ctrl+F5) is required to update the index after updating csv/efu files, but I'm really looking forward to the arrival of the automatic update feature.

Statistics: Posted by brandySnake — Fri Sep 12, 2025 5:55 am

---