I'm on Lion since the official release date. I wanted to avoid creating any issues until I had a better idea of what kinds of things are actually Quicksilver's fault (I have a few QS bugs right now), but I suppose I'll go ahead and make one for this.
»Lucas Garron On Tue, Sep 20, 2011 at 23:21, Jon Stovell <[email protected]> wrote: > The service works properly with folders on Lion, so I suppose you are > on Snow Leopard, Lucas. There are some differences, as you've noted, > which haven't bothered me but I can see how they might bother others. > At any rate, it would be good to get the proxy objects working > properly. The best thing to do is to add your input on the bug tracker > at https://github.com/quicksilver/Quicksilver/issues. > > On Sep 21, 12:54 am, Lucas Garron <[email protected]> wrote: > > I've been using the service as a stop-gap because I had the same issue, > but > > I thought I'd point out some problems I've been having with this compared > to > > my old "Select Finder Selection in command window" trigger: > > > > 1. "Send to Quicksilver" doesn't work on the folder of the Finder window > > itself - only on a selected file/folder if it is selected in it. > > > > 2. I have Quicksilver in my Dock, and when I "Send to Quicksilver" the > > application focus changes from Finder to Quicksilver. Annoying if I > selected > > the wrong file by accident, because I have to Alt-Tab instead of just > > dismissing Quicksilver as usual. > > > > 3. The first QS field is selected by default instead of the second. This > is > > only an issue out of a matter of habit, but I've gotten used to typing my > > action immediately. > > > > 4. This doesn't fix triggers that use the "Current Selection" or "Finder > > Selection" proxies. I have a few of this for opening files in specific > > applications quickly. > > > > 5. Cmd-Alt-G still seems to be buggy (not sure by how much). > > > > These are details, but they go counter to my experience of "you can make > > everything work in Quicksilver, and you can make it work *correctly*. My > old > > trigger used to work just fine. > > I'm living with the service because it's not the end of the world (and > I'd > > rather have QS select no file rather than the *wrong* file), but it's > still > > a bit annoying. > > > > I don't know what the issue is or what to do about it, but I thought I'd > > document these issues if anyone cares to know. > > > > »Lucas Garron > > > > > > > > > > > > > > > > On Mon, Sep 19, 2011 at 14:19, Jon Stovell <[email protected]> wrote: > > > Instead of the Current Selection proxy, I recommend using the Send to > > > Quicksilver service. It works every time. > > > > > On Sep 19, 9:30 am, Rob McBroom <[email protected]> wrote: > > > > On Sep 19, 2011, at 5:46 AM, AdamAL wrote: > > > > > > > After upgrading to Lion, I often experience that invoking QS with > the > > > > > current Finder selection doesn't do so consistenlty. It is often > like > > > > > QS sometimes keeps a previously selected file and doesn't get the > > > > > actual current finder selection. > > > > > > > Example: > > > > > I select file (file1) in Finder. > > > > > Press cmd+alt+space to invoke QS with the file chosen. > > > > > > ⌥⌘Space doesn’t do anything (in Quicksilver) by default. What do you > have > > > it mapped to? > > > > > > -- > > > > Rob McBroom > > > > <http://www.skurfer.com/> >
