Quicksilver

Suggestions for what to do having encountered a QS-related difficulty

• Would like to know how to get started w/ QS

  • Check out the link in the first post this topic or the in-progress Quicksilver User's Guide (PDF)

• Would like to learn how to use QS more fully

  • See previous item

• Unable to appropriately handle downloaded file for QS

  • If the file you downloaded ended in .bz2, try removing the file extension and double-clicking on the result. This may be related to 'Safari: Downloaded file's filename may have an additional extension'.

• QS crashes on start up

  • Ensure QS is not running
  • Move all files under ~/Library/Application Support/Quicksilver/Shelves/ out of the way
  • Restart QS

• Plug-ins don't seem to remain installed

  • Check for the existence of the folder ~/Library/Application Support/Quicksilver/ and the ownership/permissions of it and everything it contains (may need to be readable/writable by the account that is running QS)
  • If you don't understand what ownership and permissions are, consider reading 'Troubleshooting permissions issues in Mac OS X'

• QS is slow

  • Estimate the number of items in your Catalog -- unfortunately, this appears to require manual counting and navigation of the catalog preference pane
  • Some people report decent performance w/ 3000 or more items -- compare your estimate
  • If the number is significantly higher, consider whether all of those items need to be in your Catalog
  • Consider the 'Catalog' section of the in-progress Quicksilver User's Guide (PDF) for tips on understanding and tweaking your catalog

• QS crashed and I have a crash log but I don't know what it means

  • The following might help to gain some insight: Technical Note TN2123

• QS is not working as I expect

  • Observe your mental and emotional state
  • Write out a description of the steps you follow and the results you see to observe the mismatch between your expectation and reality -- also write out a description of your expectation
  • Save this somewhere private
  • Read through your description a few times and let it sit a while
  • Attempt to search for similar situations on the forums and/or bug tracker -- try various keyword combinations
  • If you have not managed to locate any similar reports, read over your description and attempt to imagine that someone else who has not been present to observe what occurs on your machine might read it and try to provide assistance
  • Consider improving your description and do so if it seems necessary
  • Consider an appropriate place to post your description
  • Post your description to the determined location

last updated 2 years ago #