On Sun, Jul 24, 2011 at 09:35:41PM +0000, corvid wrote:

What if it was like:

Search [Fl_Choice]

[Fl_Input]

[Fl_Button] [Fl_Button]

Yes, I thought of it, and also about just a down arrow, but receeded. 1.- Down arrow . . Search: [ ][v] [Fl_Button] [Fl_Button] . . It is less visible (and not obvious) and may be expected to bring past search strings. 2.- . . Search: [Fl_Choice]: [ ] [Fl_Button] [Fl_Button] . . It brings attention first to [Fl_Choice], and in most cases, it's better to focus it first on the text input (and when the user wants a secondary search engine he knows beforehand he'll be changing it). It breaks just hitting tabkey to change search engine quickly. -- Cheers Jorge.-

On Tue, 26 Jul 2011 14:55:34 -0400, Rogut?s Sparnuotos <rogutes@googlemail.com> wrote:

What about less dialogs and better reuse of the location bar? One could define some engines in dillorc: search_g = google.com/search?q=%s search_yahoo = search.yahoo.com/?q=%s and type the keyword followed by a search string in the location bar: g some search string yahoo some search string

I've thought of adding something like that myself, actually. Opera does that, and it's the only way I search now. ~Benjamin

On Tue, Jul 26, 2011 at 07:30:39PM +0000, corvid wrote:

Rogut??s wrote:

...

What about less dialogs and better reuse of the location bar? One could define some engines in dillorc: search_g = google.com/search?q=%s search_yahoo = search.yahoo.com/?q=%s and type the keyword followed by a search string in the location bar: g some search string yahoo some search string

Hmm, it _would_ be nice to be able to define location bar macros.

It would be quite simple now that there's a PREFS_STRINGS type. e.g. search_macro="g http://google.com/search?q=%s" search_macro="yahoo http://search.yahoo.com/?q=%s" and it would please both CLI and GUI oriented users. -- Cheers Jorge.-