#Keyboard maestro tap install

This means Hazel has to scan that folder each time it runs, which is not all that much system overhead, but it occurred to me that I really 'should’ have this run more like a cron job, once daily at 12:01 AM to rotate log files, since there is really no need to check the folder any other time. Hazel monitors that folder and renames log files each day to a file with the date appended, so there is a new log file every day, and after 10 days deletes a file so they don’t accumulate beyond bounds. I have a “.logs” folder where many of my homegrown scripts write log files with their operations for documentation and/or debugging. I have been working on a macro for a specific purpose. In the aftermath of David’s KM Field Guide, I’ve been playing a lot with KM, and realized that there is a use for KM’s ability to handle files in another way, however. I have not, to date, used KM for automation despite its ability to trigger “monitor a folder for changes.” I prefer as much as possible to keep a given task with one app to avoid redundancy, confusion, and conflicts. Hazel has long been my go-to app for file automation, using its rich set of tests and actions, often supplemented by my own scripts in bash, AppleScript or python. There is much overlap between these various utilities, and I am always debating whether to create an Alfred workflow or a KM macro. 1Password is needed for activation keys and passwords for everything else, and Dropbox is needed for data syncing for Alfred, KM, etc and so goes second) I am so used to typing ⌥-Space that I pretty much cannot use anyone else’s Mac or launch an app without it.

#Keyboard maestro tap install

In fact, Alfred is the third app I install (for those who are curious, the first two are 1Password and Dropbox, in that order. I consider Alfred, Hazel, and Keyboard Maestro to be “must installs” on every one of my Macs.