On Jan 4, 2013, at 11:36 AM, will <[email protected]> wrote:

> Web searches[^1] in the manual don't follow my workflow. I *do not* want to 
> "(Duc)k Duck Go" [tab] "(Se)arch for..." [tab] "Type more shit". I could use 
> the mouse faster than that.

For me, searches can be done with just: g ↩ more shit ↩

That’s good enough for me, so I never bothered setting up a trigger, but others 
certainly do.

(‘g’ matches DuckDuckGo by default for me.)

> The manual does make reference to setting up a Trigger which is the workflow 
> I want, but that isn't working for me. Essentially, I want to have some text 
> selected, open QS and "DuckDuckGo", so to speak. I don't want a Trigger 
> hotkey, I never remember them. I'd rather just have the actions working.
> 
> Seems there was something wrong with "Current Select". Does this mean it's 
> still out for grabs?[^2]

I had forgotten about that. It still appears to be broken.

In any case, since it sounds like you want to search for the current selection 
using Quicksilver’s interface, and not by using a trigger. That can be 
accomplished by grabbing the current selection with ⌘⎋ and calling up the Find 
With… action. Two things that will speed this up:

  1. Enable the “Focus action when displaying results” preference. That will 
mean the action is already selected after you hit ⌘⎋ so you can just start 
typing ‘fw’ or whatever. You could of course make Find With… the default for 
text if that makes sense for you.
  2. The search you use most often should appear by default in the third pane 
as of B71.

So, once Quicksilver learns what you use most often, you should be able to 
search for the current selection with just 3 keystrokes: ⌘⎋ f ↩

Or if Find With… is the default for text, just 2: ⌘⎋ ↩

> I've noticed that "current selection" doesn't seem to really be grabbing 
> selected text. "Speak" or "Large Text" show up as options, but I don't see 
> any action preformed. Actually, with "Large Text" I get a system beep 
> indicating something is wrong.

I see this with some text in Safari, but not all. Some page layouts might 
confuse the selection process. It seems to work reliably in all other OS X 
applications.

-- 
Rob McBroom
<http://www.skurfer.com/>

-- 
You received this message because you are subscribed to the Google Groups 
"Quicksilver" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en.


Reply via email to