Use Everything to search for all descript.ion files containing the specified string.
Get files that match the description from these .ion files,
and add them to a file collection.
So the search speed is very fast!
“Save descriptions to internal file metadata if possible” Is this checkbox mandatory? If it is checked, comments added to some files will not be written to the descript.ion file and will not be searchable by this plugin. If it is not checked, the comments will be lost if you move an annotated file to another folder.
Thank you, the issue with lost copies has been resolved. However, I'm still wondering why, when this option is enabled, some descriptions are written to the descript.ion file while others are written to the file metadata. Are there any rules for writing to the descript.ion file and file metadata? Which files are not written to the descript.ion file, and which files are not written to the file metadata? Can I write to both the descript.ion file and the file metadata simultaneously in DO?
Indeed, this error so far has always turned out to be a misperception. When a comment is in both NTFS and descript.ion, deleting one of both will not delete the other one.
In addition, especially for a value taken from descript.ion, you need to do a refresh of the lister view (F5).
PS. A good script for working with descript.ion can be found here:
You can write anything to multiple types of metadata simultaneously with a script. But you cannot write to both descript.ion and to the NTFS (ADS) extended comments as far as I know - because in both cases the field 'description' (or 'userdesc') is used, and this field will redirect your comment either to ADS or to descript.ion. This is an implementation choice made by the Opus guys.
