quicksilver/Quicksilver — pull request #506 by pjrobertson (2011-10-16 11:27:56+00:00)
Title: Mechanism for sniffing for faulty plugins

This kind of goes hand in hand with the plugins system stuff. I though - why not have QS take a note of the plugin that's causing it to crash?

Then, the next time QS launches, it can inform the user of a faulty plugin, and attempt to delete it!

There's also one pull request here that deletes several paths which I thought of as unneeded.
Basically, QS would look for plugins in these folders on launch, which I thought was unnecessary `/tmp/xxx` paths are 'relative to the current path' and 'relative to QS.app':

` "/Network/Library/Application Support/Quicksilver/PlugIns",
"/tmp/QS/build/Debug",
"/Library/Application Support/Quicksilver/PlugIns",
"/tmp/QS/build/Debug/PlugIns",
"/tmp/QS/build/Debug/Embedded/PlugIns",
"/private/tmp/QS/build/Debug/Quicksilver.app/Contents/PlugIns",
"/private/tmp/QS/build/Debug",
"/private/tmp/QS/build/Debug/Embedded/PlugIns",
"/Users/patrick/Library/Application Support/Quicksilver/PlugIns",
"/private/tmp/QS/build/Debug/PrivatePlugIns",
"/private/tmp/QS/build/Debug/PlugIns"
`

I've reduced the list down to just QS.app and the app support dir