p.s. what did the ones prefaced qss-http mean?
I don't think there should be a difference between using qss-http and just http but I seem to recall there were some instances where it worked better (perhaps due to a bug).
Howard
--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 blacktree-quicks...@googlegroups.com.
To post to this group, send email to blacktree-...@googlegroups.com.
Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
That's what's happening when I use the search "http://www.allmusic.com/search/all/***"I get redirected to the homepage. Quicksilver is not including the HTTP or WWW in the URL.
--
You received this message because you are subscribed to a topic in the Google Groups "Quicksilver" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/blacktree-quicksilver/gj5z5qmQjt0/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to blacktree-quicks...@googlegroups.com.
I fixed the problem. For some reason my trigger was not using the source I had added to the web search list, it was using another source.
I'm still having intermittent problems with my triggered searches. Usually on startup, a search shows no results. If I restart QS a couple of times, the searches start "taking" again. Any ideas?