I know, it's annoying. To be honest it shouldn't be too hard to fix since we should be able to use git and git bisect good / bad to find which commit actually broke the triggers, then change it back (since it was all working before that).
Maybe when one of us gets some time we'll be able to fix it. My solutions at the moment are to either: a) Add triggers using an earlier version of QS b) Add a triger in b58, open the ~/Library/Application Support/Quicksilver/Triggers.plist file BEFORE quitting QS. Save the file, then quit QS, then save the file again. Sometimes it takes a couple of repeated 'saves' to the file but I can normally get the trigger to stick. I may get some time in the next few weeks, but as usual - nothing's certain! If you want to help, you could learn about git, git bisect and finding a bad commit and how to build in Xcode. Basically all you'd be doing is getting git to find which commit broke the trigers. You'd do this by checking a commit version by building it in Xcode, if it works you tell git it's good (if not you tell git it's bad) then you'l hone down to the exact problematic commit. On 27 October 2010 05:27, BryanW <[email protected]> wrote: > I wish I had the knowledge to fix the triggers problem in version ß58 > (3841) but unfortunately I don't and I was curious if anybody knew if > this was being worked on or if I'm just missing something. Triggers > won't save and I can't even invoke QS with a selection or in text- > mode. I assume everyone running 3841 has the same problem.
