This update broke quicksilver for me…..arrrghh…

Same here, this broke quicksilver for me. Can’t type properly anymore.

Hey Merlin, do you know if this build fixes the “Show Menu Items” trigger that you covered on 43f a while back? I became absolutely addicted to it in Tiger, and it’s the feature I miss most in Leopard (besides working application scopes, that is).

When I heard the drain gurgling after alcor started yanking the plug so many months ago I made the jump to Launchbar. It’s not as good as Quicksilver in some cases and better in some others.

I may give Quicksilver another try, but it’s hard for me to devote my time to an app standing on a slippery rug.

I, too, switched to LaunchBar (http://www.obdev.at/products/launchbar/index.html) about half a year ago. I was starting to encounter a lot of flakiness with Quicksilver and was tiring of restarting it or having it bomb entirely. It’s not productive if it does not stay running, right?

Mind you, I loved Quicksilver. I am hoping that the rewrite brings it back to the “no crash zone”. I have used rooSwitch for over a year now, and that is one fine little app that I discovered on MacZOT! by accident. I’m glad I did. I use it to manage apps with not only multiple configurations, but also with some different test databases and data sets. Very handy.

I suppose I’ll give Quicksilver another look-see when I get some free time.

I too switched to LaunchBar after it kept crashing. Alcor himself recommended it.

Although I loved Quicksilver, now all my shortcuts and muscle memory are with LaunchBar and I don’t think I’ll switch back.

Quicksilver might be on the mend but it is too late. I’m currently using launchber.

I don’t know how accurate these statistics are, but glimpsing at wakoopa data you may see that Quicksilver has been used by 1764 people while Launchbar by only 85.

http://wakoopa.com/search?query=quicksilver&os=mac

I know these are just estimates and we can only deduct some rough percentage of the “market penetration”. I don’t advocate any of the apps, although I am a Quicksilver fan, just pointing that the new release might make a lot of people happier…

I have to concur with the rest of these commentators, it didn’t work for me either. That said, it’s clearly at the alpha stage and as such should be treated with extreme caution.

Downgrading to the version on blacktree.com fixes the problem.

I never gave up on Quicksilver; not for LaunchBar — not for the improved-in-Leopard Spotlight. The crashes and CPU-hoggery while rescanning are frustrating at best, but those same crashes remind me of just how dependent I am: when QS dies, I’ll freeze up too…………..and will stare at my screen for 30-60 seconds just trying to remember just how to use it without my precious Opt+Space.

Yes, yes, I know: nerrrrrrrd. Say what you will, but I can’t fathom a Mac without Quicksilver. Thanks for pointing to a life-affirming update, Merlin.

I would suggest that you all look at the builds that Ankur (http://lipidity.com) is building. He is also cleaning up the code and is in the process of talking with Alcor about merging his branch with the main branch.

I ask that you don’t bug him too much, because I (and a fair amount of others) have been asking him every other day when the next release is going to be out.

You can download his latest version here: http://lipidity.com/software/quicksilver/

I’m yet another LaunchBar defector. I used QS primarily as a launcher and a Finder alternative, and I’ve been just as happy with LaunchBar. Plus, it’s snappier and more stable.

downloaded and installed the latest version, and everytime it launched it would immediately quit. Had to go back to the older, stable version.

The update broke my quicksilver too - I removed quicksilver, and all its support files, and tried again; I’ve found that I can reproduce the error by installing the ‘File Tagging Module’-plugin.

edit: also, ‘social bookmarks’ is broken; I can reproduce the error by adding my delicious feed to the qs catalog.

It would be nice if someone could confirm this.

Ah, it turned out I had the Shelf plugin installed, and this was making it crash within seconds. I never use it so I just removed it.

Is there a feature where you can call the “Append Text..” action but direct it to .rtf files “that are already open”? I’ve encountered problems using non-.txt files or .txt files that are already open with that action and the “Append Text” feature I think, personally, is one of the most impressive of QS’s already bodacious framework.