Mr_Noodle wrote:I'm not sure why you have the nested condition there but have you looked at the Sync chapter in the manual? There's a rule there which uses Hazel's Sync action, which is rsync under the hood.
As per my initial post the nested condition is to induce a delay. Otherwise when I created a document in a watched folder I was getting 2 documents created in the Rsync location: untitled.md and mydocument.md for instance. This was because the rule was triggering on creation and then on a change when I named the document a couple of seconds later. I needed enough delay to avoid that happening.
I have reviewed the Sync chapter, prior to writing this rule, the rule leans heavily on what's in that chapter. I'm using Rsync rather than Hazel's Sync capacity so I can use some of the options in Rsync to tailor the result.
None of that however addresses the issue: This rule will match if checked in the Hazel interface; it will run in a forced run in the Hazel interface; but it won't run if left to its own devices to watch the folder.
I need help in resolving that please.
