Stopping process after first match

Get help. Get answers. Let others lend you a hand.

Moderator: Mr_Noodle

Stopping process after first match Thu Oct 06, 2016 1:45 pm • by moettinger
I am running a trial version of this product and will definitely purchase it if I can make this rule work. Currently, this is what I'm doing:

I have Hazel watching the modified time of all files in a certain folder. Any time a file gets modified, I have Hazel run an Automator flow that runs Transmit sync. So far so good.

Issue is that if I save a JS file that then gets minified into another file, Hazel has Transmit open twice and sync twice. Ideally, I only want the sync to happen once. Another example would be saving a .css file that then has an accompanying .css.map file compiled. I would only want the sync to happen once. Is this possible?
moettinger
 
Posts: 1
Joined: Thu Oct 06, 2016 11:47 am

Re: Stopping process after first match Fri Oct 07, 2016 10:30 am • by Mr_Noodle
It might be better to monitor one folder level up and have your rule match the folder instead of the files. If you have a deeper file hierarchy you need to keep track of, check out this thread (it uses the Sync action but the rule conditions should still apply): viewtopic.php?f=4&t=1593#p6500
Mr_Noodle
Site Admin
 
Posts: 11872
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City


Return to Support