I'm using Hazel successfully to monitor many folders, including a huge iTunes Music folder without a problem.
However, when monitoring the ~/Library/Calendars/ folder for any changes to Info.plist or *.ics files, it fails to know a match has occurred and does not update the Date Matched field regardless of whether the script returns true or false. The folder is paused. I can preview the files (many!) within the nested subfolders and see the matching rule. I then tell Hazel to run the rules and I can watch the log to see all the files matching the rule. There is no indication of an error. I know the script is being run because if I return false, Hazel logs an error, but still does not update the preview field indicating there's been an error. (It also dumps the script as a huge hex encoded field of:
- Code: Select all
OSAScriptErrorOffendingObjectKey = "<NSAppleEventDescriptor: 'scpt'($ ... $)>";
When I then preview a file that had matched according to the log, the date matched field is blank and the file still thinks it matches the same rule. It doesn't help if I monitor a single .calendar folder with many events, but if I monitor a test calendar with a single event, it works fine. Is there something magical about the Calendars folder … or many files in a folder?
A related question is … since I'm debugging the script, I'd like to reset the Date Matched so that I can force a match again and run my script. The only way I can find to do that now is to delete the monitored folder and add it back, which is not fun, or to touch the file to change it's modification date, but that is undesirable. How can I reset the match status of one or all files?