it most definitely is, i just moved the quicksilver prefs and app support away to test it again. clean quicksilver multiple tests. type fire and firefox will show up much slower in the a5 than it will in the a4. a5 won't show the fire underlined before the end of your typing. a4 will.
you won't notice it when using primer because primer will show the search text seperately from the search itself. id test it out but the quicksilver codebase is far from "build&run" regards On Mar 14, 4:01 pm, Chris Cairns <[email protected]> wrote: > This in not an a5 issue. I have not faced it, nor has any other user > reported it as much as i know. So, the issue is specific to you and > there can be several reasons which can be found out and the problem > can be fixed. But, since you mention that you have already switched > back, let us know if you want to know more. (Also remember, third pane > is broken in a5)
