Thanks Howard

On Nov 7, 4:01 pm, Howard Melman <[EMAIL PROTECTED]> wrote:
> On Nov 6, 2008, at 8:33 PM, chris burgess wrote:
> > Periodically, Quicksilver stops showing results for my Applications  
> > folder.

> To rule out user error, the first things to check are:
>
> What stops working? is it a single app?  several apps? all apps?  
> anything (or everything) else?

All apps - Quicksilver finds lots of document matches, but fails to
return the results it would normally do (eg, "te" matching
"Terminal").

> QS matches against it's catalog which is defined by what's checked in  
> the Catalog Preferences. Make sure the sources of the things you're  
> missing are checked. E.g. if it's an Application is it in /
> Applications or ~/Applications or somewhere else? Is that location  
> checked and is it scanned (there should be a number next to the  
> catalog source in the Catalog Preferences. You can also select a  
> catalog source, click the i button at the bottom to have the drawer  
> open and check the middle tab, Contents, to see if the item you expect  
> to be there actually is (and that it's checked).

All my apps are in /Applications, and that is the first checked source
in my catalogues. I don't have "find all applications" checked.

I'll your other questions a desktop sticky and check them next time
the bug recurs. Right now, they all look normal, but right now I'm not
experiencing that problem :)

> I recommend unchecking Find All Applications, particularly if you have  
> external drives connected. It does a scan of the entire drive (all  
> drives) to find applications. This is slow and certainly not something  
> you want happening against a backup drive.

I presume this is the default, or I've forgotten setting it that way
if not.

> If the item is in the catalog and not found in the first pane of the  
> command window then something is pretty broken. Check in Console.app  
> under Console Messages for any messages with Quicksilver in them (you  
> can use the search box). There might be a clue there.

Again, will follow this up next time the issue recurs.

Thanks for your feedback and guidance.

Cheers

Chris

Reply via email to