Ok thanks, that's good to know! Since the url isn't the problem, then, do you have any idea why it's not working properly? From the section of the manual that you quoted above, here is what isn't working for me:
If you specified the argument in the trigger it would search for the same text each time it’s run. However, if you leave the third pane blank, then when the trigger is run, Quicksilver will open a command window with the first two panes filled in (in this case with Wikipedia Quicksearch and Search For…), and the third pane selected, ready for you to type the query. Quicksilver is also smart enough to realize that the Search For... action wants a text argument and puts the third pane in text mode for you. Even though I am leaving the third pane blank, when I run the trigger I get a browser-launch instead of a third pane ready for me to type the query. My trigger definition is nearly identical to the one shown on page 41 of the manual, except the different url... On Aug 24, 9:43 pm, Howard Melman <[EMAIL PROTECTED]> wrote: > As long as there is a *** or %s in the url, QS should recognize it as > a web search url. I've used both http and qss-http urls. The web > search URLs in the catalog source should be fine. If you define your > own custom web search urls, If one doesn't work, try the other. > > http is the network protocol of the web. URLs that begin with http > tell the browser to use the http protocol to send a GET request. Some > web forms you fill out use a POST instead of a GET request and there's > no way to specify that in the URL (you specify that in the html of the > web page). To enable web searches in quicksilver to use POST requests > for those sites that require it, it recognizes qssp-http: URLs (notice > the p before the -) which tells QS to use a POST. I think the qss-http > (without the p) was just created to be similar to the other one. I > otherwise haven't found a real difference between it and http:. > > Since I do use a custom web search catalog entry with just the 30 or > so searches I use, I have changed them to use qss-http so that when I > try to select them in the QS command window I know I'm getting one of > my QS web search urls instead of a bookmark from safari or some other > place (which would all just be http: urls). > > Howard > > On Aug 24, 2008, at 9:26 AM, Ian wrote: > > > Thanks a lot! I've actually been using that manual as a guide, it's > > where I learned that you can assign triggers to processes like this in > > the first place! There's one thing that doesn't match 100% with what > > I'm doing and what appears in the manual, but I'm not sure how to > > change it. In the Manual, beneath the Wikipedia Search icon there's a > > short url that startshttp://etc.etc. When I enter the Wikipedia > > search on my computer, though, the url begins qss-http://etc.etc. I > > believe this comes from the Web Searches plug-in, which I have > > installed, and is one of the 600+ searches that is scanned by the Web > > Searches module in the catalog. > > > Is there a difference between the two? And, if so, how to I get > > Quicksilver to point to the correct ones? > > > Thanks again for all the help > > > On Aug 24, 8:43 pm, Howard Melman <[EMAIL PROTECTED]> wrote: > >> The following is from page 41 of the manual which includes a > >> screenshot of what the trigger definition should look like (the > >> example uses a Wikipedia search but it works for a google search > >> too).http://mysite.verizon.net/hmelman/Quicksilver.pdf > > >> Some actions take an argument in the third pane and triggers can use > >> these too. The Search For… action will search some web site for the > >> text entered as an argument. See the Web Searches section for the > >> details of using this action. A trigger for a commonly used web > >> search, such as Wikipedia, is very useful. If you specified the > >> argument in the trigger it would search for the same text each time > >> it’s run. However, if you leave the third pane blank, then when the > >> trigger is run, Quicksilver will open a command window with the first > >> two panes filled in (in this case with Wikipedia Quicksearch and > >> Search For…), and the third pane selected, ready for you to type > >> the > >> query. Quicksilver is also smart enough to realize that the Search > >> For... action wants a text argument and puts the third pane in text > >> mode for you. It even fills in the default text from the OSX Shared > >> Find Clipboard (which you can set in many Cocoa applications with > >> ⇧⌘E). Note, if the third pane isn’t empty when you create the > >> trigger and you want it to be, you can type ⌘X to cut out whatever > >> is > >> there. > > >> It goes on to describe using proxy objects to allow you to do a > >> search > >> on highlighted text in any app. > > >> Howard > > >> On Aug 24, 2008, at 7:30 AM, Ian wrote: > > >>> I use Quicksilver to search the web a lot, and I'm trying to skip a > >>> few steps. I understood that you can assign a hotkey that will do > >>> the > >>> first two steps in an argument so that you just have to do the final > >>> one. > >>> For e.g.: I'd like Command-Shift-G to bring up Quicksilver with the > >>> final step of a "Google Search" + "Search For" (Text) argument so > >>> that > >>> all I have to do is type Cmd-Shift-G and the Quicksilver text box > >>> pops > >>> up and I can type my search and be whisked away to google. > >>> When I go to assign the custom trigger in the preferences, though, > >>> what happens when I press the hotkeys is it launches safari and > >>> gives > >>> me to the google homepage. While this is kind of convenient, it's > >>> not > >>> really what I have in mind. > > >>> Any solutions? I'm running B54 on the most current version of > >>> Leopard. > > >>> (PS. Another related annoying problem. When I go to program hotkeys > >>> Quicksilver never actually shows me what the hotkey combo is in the > >>> Edit pane. For example, if I want the hotkey to be Cmd-Shift-G the > >>> only thing I see is Cmd-Shift . . . no G. Not a huge deal, but as I > >>> add more hotkeys it'd be nice to have them visible so I can remember > >>> what's assigned to what . . . )
