There is actually a way to uncorrupt your triggers.plist file. Instead of deleting the file, double-click on it (make sure Quicksilver isn't running). It should open in a program called Property List Editor. If not, try to find this program. Once it opens, click on the arrow next to the word "triggers" to expand the list. You should see a list of items (creatively named Item 1, Item 2, Item 3, etc.) that you should expand by clicking on the arrows. Under each item are some variable names, such as "ID", "command", "enabled", "name", "type", and some other names. Look for an item without a "command" variable. This is the corrupt item that Quicksilver will spend forever trying to load. Once you delete this item, Quicksilver should run perfectly.
On Feb 20, 10:31 pm, Chris Cairns <[email protected]> wrote: > Probably your trigger have become corrupt. To fix it you will have to > deletetriggers.plist in ~/library/applications support/quicksilver. ( > ~ stands for your home directory not root). You will have to create > all existingtriggersagain after doing this. > On Feb 21, 2009, at 2:52 AM, carrotsandsmarties wrote: > > > > > Hi - > > I use quicksilver everyday, all the time, but I rarely have to change > > anything - however, I want to set some newtriggers, I click on the > > thetriggerspane, but it hangs up, never opens. Anybody know if > > there is any other way to get in totriggers? > > > I haven't made any changes to my computer, I have OSX 10.5.6 and the > > last version of QS. > > > Many thanks > > Carrotsandsmarties.
