ChrisB

I could be wrong, but I thought that the Caffeine utility is essentially a more user-friendly interface to trigger caffeinate without needing to open (or keep open) a terminal window. Caffeine has to be the most useful little utility for its size in all of Mac utility offerings!

I figured it out. My Alfred 2 folder didn't have a "websearch" preferences plist file. In fact it didn't even have the /preferences/features/websearch folder at all. That's what was causing the migration script to fail. To "fix" it, I simply created a dummy custom search, which then created the /preferences/features/websearch/prefs.plist file, and then the migrate script worked perfectly. Hopefully that helps you refine the script, or refine Alfred itself.

Okay, I've moved it, but still get the same error. Steps I took: - clicked Set Sync Folder - created a new folder called "Backups" (because I don't really want "Alfred" at the top of my dropbox, since dropbox is already cluttered enough by other apps that want the top level) - created my AlfredApp folder in there So this shows in Alfred now as: ~/Dropbox/Backups/AlfredApp It asked me to restart Alfred, which I did. I verified that Alfred had indeed copied the prefs file over to the new folder. Dropbox sync was very fast. Running "migrate" still gives me "Error: Unable to locate v2 preferences". Would moving the Sync folder back to someplace outside of Dropbox make any difference? Isn't Dropbox just like any other local folder as far as the OS goes? Is there an option in Alfred 2 to turn off sync and go back to the default Library location?

I have my v2 set up with Syncing pointed to ~/Dropbox/Apps/AlfredApp When I run migrate, I get "Error: Unable to locate v2 preferences"

Hi rice.shawn, great idea! There's a preliminary packaged workflow for a similar workflow, with a few more features in it, hosted on github at: alfred-caffeine-controls It seems to work okay, but I found I disliked a few things about it: a. if I've got caffeine enabled already and give it a new time, it toggles it off b. it only supports "on", "off" and "X" seconds, not hours I've written fixes for both of these but haven't submitted a pull request for it yet. I'll aim to do that by the end of the week.