On Sunday, November 15, 2015 at 7:02:21 PM UTC+1, Rob McBroom wrote: > > I think you have that backwards, which is why I didn’t understand at > first. You want to leave ⌥→ alone and map another key to do what it does. >
Sorry for the confusion. You got it right. > Without changing the code, the only thing I can think of is an AppleScript > that “presses” ⌥→. You could then create a trigger scoped only to QS that > runs that script. I don’t know if it would actually work though. > You could also use something like Karabiner, but I think that would change > they key in every application. > Karabiner provides per-app granularity but AFAIK not context awareness as this would require. And I would leave AppleScript for this. Like I said, there’s no method that just shows alternate children. There’s > one that shows children, and it checks to see if ⌥ is being pressed in > order to decide what to show. Anyway, since / works also for moveRight: in DefaultBindings.qskeys and the modifier is verified later, ⌥/ works also. Curiously, ⌥⌃L doesn't. Can you point me to the code that checks for the modifier? I think it's this one <https://github.com/quicksilver/Quicksilver/blob/66effe80e48fa6f1ee43989699ba4309592e3857/Quicksilver/Code-QuickStepInterface/QSSearchObjectView.m#L1743>, but I'm not sure. -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/d/optout.
