looking forward to a fix since I think no quicksilver could be a  
dealbreaker for me.



On 17 Jun 2009, at 19:34, "Sam" <philosopher....@gmail.com> wrote:

>
> I am very happy to have been corrected.  Since I'm very new to the OS
> X platform (happy switcher here), I'm thrilled to find out it probably
> won't be hard to get Quicksilver working with Snow Leopard.
>
> On Wed, Jun 17, 2009 at 8:17 AM, Mohammad Haque<batman...@gmail.com>  
> wrote:
>> This is not true. QS is not/does not use InputManagers to do it's  
>> thing.
>> Also, InputManagers do work in Snow Leopard. You just need to get  
>> 64/32-bit
>> compatibility right.
>>
>> Not sure how much more can be said given that everyone with access  
>> to Snow
>> Leopard is bound by NDA.
>>
>> On Tue, Jun 16, 2009 at 11:41 PM, Sam <philosopher....@gmail.com>  
>> wrote:
>>>
>>> I read somewhere that Apple has removed support for InputManagers
>>> (which Quicksilver is or uses) in Snow Leopard.  This is very
>>> disconcerting to all of us Quicksilver users.
>>>
>>> On Tue, Jun 16, 2009 at 7:54 PM, astav<ast...@gmail.com> wrote:
>>>>
>>>> i tried it too, don't work. Don't know what is going on though.
>>>>
>>>> On Jun 16, 5:04 pm, "D. Ebdrup" <debd...@gmail.com> wrote:
>>>>> Given that I just got access to a seed asset of OSX Snow  
>>>>> Leopard, I
>>>>> installed it and after installing it I noticed that Quicksilver no
>>>>> longer works. If you need bug reports or such, just instruct me in
>>>>> what to do and I'll do what I can to help.
>>>>>
>>>>> Having said that, it's incredible how much one relies on ones  
>>>>> launcher
>>>>> - one really notices it when it's gone. :(
>>>>
>>
>>
>
> >

Reply via email to