It seems that β56a7 has some bugs regarding triggers. You can try quitting QS, dragging ~/Library/Application Support/Quicksilver/ Triggers.plist to the desktop, and then restarting to see if you can now set up your triggers properly. If that doesn't work, you might just have to hang on for a new build to come out with a fix.
On Sep 17, 1:31 pm, Ian <[email protected]> wrote: > Hi, everyone: > > Hope someone has run into this and has a solution: I've looked all > over the place and found similar issues whose fixes did not work for > this problem. Here it is: > > 1. I create a custom trigger to execute a web search (say YubNub, for > example) > > 2. I create the trigger as I did under b54 > > 3. Trigger does not immediately function (this issue has been well- > noted). I deactivate the trigger and re-activate it: trigger works > normally. > > 4. Quicksilver restarts, usually because I restart the computer. > > 5. Trigger disappears: web search address replaced with <null>; > trigger effectively gone, even though it has a space on the custom > trigger list. > > Now, I'm sure some other intermediate Quicksilver users can > sympathize, but going without these triggers is like losing one's > sense of touch. I use triggers to go to wikipedia, hulu, google (all > services), library catalogs, foreign language dictionaries...that's > just off the top of my head. > > A fix for this would earn my heartfelt gratitude. Thanks for your > time, > Ian
