I also have mixed success with triggers. Here is some info for the Quicksilver developers that I hope will help them fix the triggers bug. Case 1 works, case 2 fails:
1. I can create a new trigger that opens a text file that lives on my Desktop "Open filename.txt", it is saved to triggers and stays there on subsequent Quicksilver relaunches. 2. However, when I create a new trigger that opens a text file in the / Applications subpath "Open filename2.txt" it works until I relaunch Quicksilver, and then the trigger entry shows up as "Open (null)" and does not respond to the trigger. After case 2, I inspected the ~Library/Application Support/Quicksilver/ Triggers.plist entries and verified the "/Applications/filename2.txt" path string exists in the command/directID of one of the entries. For some reason it is not getting read back in correctly or used correctly by Quicksilver since it lives in the /Applications directory. As I stated, a file that lives on the Desktop is treated correctly on relaunch. Thanks for taking a look at it! On Sep 29, 3:44 pm, adamrice <[email protected]> wrote: > So far, I've been having mixed success with getting triggers to work. > Opening defaults.plist and setting useeffects to false and deleting > the existing triggers.plist file seemed to help, somewhat. I can now > create some triggers, but not others. > > For example: I have created a trigger to open an app. That works. I > have created another trigger to bring up Google in my web browser. > That doesn't. I variously get the following results: > 1. The trigger works until I relaunch Quicksilver. After that there's > an empty trigger where it used to be in my triggers list > 2. Nothing happens > 3. My Mac beeps, but nothing else happens.
