I have been feeling QS slow down, especially as I add triggers,
actions, make catalog changes, etc., all of which store their info in
plists.

I know that Snow Leopard has changed the way it handles plists to
using them as compiled binary plists (whereas in previous OS X's you
could just open a plist in a text editor and read it in essentially
an .xml format)...

So I'm wondering if part of Quicksilver's Snow issues are related to
the way it handles plists.

Can anyone answer this? Am I way off?

Reply via email to