definitely using the latest version. i've tried using both bezel and
primer interface (favouring the latter). does that make a difference?

i've been using QS for years... i'd hate to have to give it up just
because of this....





On Jan 4, 12:45 pm, Patrick Robertson <[email protected]>
wrote:
> My only suggestion is to check the interface you are using, and that you
> are using the latest version.
>
> Are you using the built in Bezel interface, or a different one?
>
> On 4 January 2012 17:54, t <[email protected]> wrote:
>
>
>
>
>
>
>
> > i have been having quicksilver issues ever since upgrading to os
> > 10.7 / lion. i've tried reinstalling several times, and have also
> > replicated this on another machine. googling has thrown up no
> > solutions, so i'm presuming i've just go wrong settings somewhere.
> > here's what's going on:
>
> > 1. first time i setup and use quicksilver all works fine.
> > 2. if i quit qs or restart my computer then when i start it up again,
> > call up qs by control-space, then when i start typing *no text appears
> > in qs* but it does appear to be receiving input because if i hit enter
> > then it opens something up.
> > 3. however, since i don't see what i'm typing, and it doesn't trigger
> > the list of things it might open, i have no idea what it's going to
> > open. it also behaves differently from normal, i.e. typing "post" does
> > not get "postbox" as the first item, it gets itunes!
>
> > i've tried resetting preferences, uninstalling, reinstalling, deleting
> > caches in ~/library/caches, deleting shelves in /application support,
> > etc. etc. etc. also tried this on another computer and it's the same
> > behaviour.
> > i've tried not changing any of the default preferences.
> > i've checked and i'm not running any of the known problematic
> > applications.
> > the only way to reset it to proper behaviour is to quit quicksilver,
> > start it up again manually, choose "reset preferences" and go through
> > the whole thing again.
>
> > anyone have any ideas what's going on here?

Reply via email to