The way my about:config is set up, all URL-bar entries that aren't formatted like a URL are instead sent to "http://queri.ac/lenoxus/X", where X is the entry. The result … (read more)
The way my about:config is set up, all URL-bar entries that aren't formatted like a URL are instead sent to "http://queri.ac/lenoxus/X", where X is the entry. The result is that I can treat the awesomebar as a command line of sorts; for example, if I enter "fb", it redirects me to Facebook, and if I type "w chocolate", it searches Wikipedia for "chocolate". (Yes, I know Firefox has keyworded bookmarks, but Queriac allows me to easily synchronize those with other computers.)
I recently set up a wireless system for my house. The router gets input from a DSL modem which gets input from a Verizon phone line. There's a sudden new behavior going on: if the entry is not a URL and doesn't contain a space, the query is instead sent to a Verizon search engine thing called "Search Assist". I tried following Verizon's directions for turning this off (re-interpreting them for Mac 10.5), but the only result was to prevent all Web pages from loading.
In any case, it seems to me that there should be a way for the pattern to go Firefox -> Queriac-based-URL -> okay Verizon, please go to that Queriac page. How do I prevent Verizon from butting in and "trying to help" before Queriac gets a chance to receive the two- or three-letter data? Is there an about:config that could work?
For what it's worth, everything does still work fine if there's a space in the entry. If I type "w dragonfly", it will load this page, but if I only enter "w", it loads this one. So a current workaround is to type things like "fb x". I want the workaround-workaround.