I don't think it's the Web Search plugin; this seems to happen with any web address triggers that aren't recognized. I have a trigger for Google Maps that is recognized and is listed as "Open Google Maps," and that one works even after reboot. But any of my triggers that are listed as "Open http..." stop working after reboot, including calendar.google.com, docs.google.com, and www.weatherunderground.com.
So something weird is going on with the processing of http:// I guess. On Oct 28, 7:45 pm, cawpin <[email protected]> wrote: > I am experiencing a similar problem. I had a trigger set up to search > Google (CMD+G) under Leopard. It would send the query > qss-http://www.google.com/search?q=***and open the results in my default > browser, which happens to be Firefox. Upon upgrading to SL this > trigger resets to the mentioned "Open (null)" and the trigger no > longer does anything. This happens whenever QS is closed and re- > opened, including rebooting. I have another trigger to launch a > Terminal (CMD+ALT+T) window which still works perfectly. However, no > matter what keyboard shortcut I assign to the Google search action, > the action is wiped out on a restart of QS. Personally, I think this > may be a bug in the Web Search plugin. > > On Oct 12, 5:59 am, Zippy <[email protected]> wrote: > > > 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.
