Mr_Noodle wrote:If a file matches the same rule over and over, Hazel shouldn't execute the actions. If so, then something is going on. Is it possible files are oscillating between two different rules? Are these files on any sort of weird filesystem (network share, thumb drive)?
The files are all local to my Mac, so no weird filesystem. I guess there isn't a way for me to actually verify that Hazel is executing the actions multiple times. I made my assumption based on the fact that my CPU utilization would skyrocket (with Hazel using 70%+ CPU) for many minutes. I have a few thousand files being lowercased, and didn't think it would take that long to execute the actions a single time over all the files.
Mr_Noodle wrote:One thing to do is to check the logs by going to the "Info" tab and clicking "View Log". Feel free to send me anything interesting there.
I'll rerun the actions I have set up and look at the logs. I'll report back if there is anything interesting.
Mr_Noodle wrote:As for the date modified, that's a fair point. I've already put in a patch (so it should be in the next version) such that if a rename will result in the same file name, it doesn't actually do the rename. Though, file renames affect the modification date of the containing folder, not the file itself. If you are observing the modification times of the files themselves being changed, then I suspect something else is going on.
I'm not sure which modification time was being changed (the files or the folders). I can check to see.
Basically, would it be possible to add in a feature for the rules that allows a user to specify that they want their match to be case sensitive?
Right now my rule is basically to match:
"Extension" "is" "JPG" and do the following "Rename file" with pattern "name extension (lowercase)"
Could a dropdown be placed on the match "is" to select case (in)sensitivity?