2009/6/29 Jono DiCarlo <[email protected]>: > > I'm pretty sure that Google not being suggested is because of the case- > sensitivity bug. (See > http://groups.google.com/group/ubiquity-firefox/browse_thread/thread/489b382eb420a265 > ) > We have a fix for this bug already, and it will be included in the > final version of 0.5 to be released this week, so "g" or "go" will > once again complete to "google". > > Timur, your suggestion about Ctrl-N and Ctrl-P is very interesting. > You must be an Emacs user, right?
No, I'm a Vim user :) But I also use command line extensively and find Ctrl-combinations very handy. Actually, incompatible navigation and editing shortcuts in different kinds of applications (shells, input fields in browsers and other GUI apps etc.) is a bit of problem for me. I've been even thinking about making my own keymap where some shortcuts can be used instead of arrow keys, Enter, Backspace etc. Here's a very interesting blog post about this http://duartes.org/gustavo/blog/post/home-row-computing > I am to, and I often find myself > trying to use ctrl-N and ctrl-P in other applications... I think we > could consider adding those as an equivalent to the up-arrow /down- > arrow keys; it would be a benefit for Emacs users and it wouldn't hurt > anybody else. As Christian noticed, these combinations are already used for new window and print. I wonder if it's safe to redefine them when Ubiquity is active. > But back to the main question: there are definitely a few questionable > rankings making it in to the suggestion list with the new parser. We > may have to tweak some of the weights of the various factors that go > into sorting the suggestion list. We should start a conversation > about that over on [email protected]. > > --Jono > > On Jun 28, 9:54 am, palousegeo <[email protected]> wrote: >> I've found the same situation on WinXP. I've had a bit more luck using >> "s" (for search), but I miss doing "g tab" search term. When I tried >> "Google", search wasn't even one of the options. >> >> -Rick >> >> On Jun 26, 11:48 pm, Timur Izhbulatov <[email protected]> wrote: >> >> > 2009/6/27 Brandon Pung <[email protected]>: >> >> > > So it sounds like there are two things you were asking about here. First >> > > is >> > > that "goo" is returning "add to google calender" as the top suggestion >> > > instead of the verb "Google (search term)", when you would expect "Google >> > > (search term)" to be the top choice. Your second concern is that you >> > > can't >> > > tab to cycle through the suggestions. >> >> > > For your first thing: I agree that "go" should have "Google (search >> > > term)" >> > > as the top suggestion. It seems to be a problem with case sensitivity. If >> > > you type "Go" then "Google (search term)" will be the top suggestion (at >> > > least it is for me). In fact, even just "G" is giving "Google" as the top >> > > choice, which is good. So we should make sure our matching to verbs is >> > > not >> > > being done with case senstivity, because I don't think it should care >> > > about >> > > the case of the letters here. Good catch! >> >> > Hm... I have "google" in the suggestions, not "Google". >> >> > Unfortunately, now I can't reproduce my issue with calendar reliably. >> > However, there are some things that I noticed: >> > * the problem appeared right after update >> > * there was only one browser window with many tabs >> > * there problem disappeared in new window >> >> > I also tried unsubscribe/subscribe on the calendar command feed and >> > restarting the browser, but it didn't help to reproduce the problem. >> >> > > For the second thing: We want to keep the behavior of tabs doing tab >> > > completion, instead of cycling through suggestions. Arrow keys seems >> > > like an >> > > intuitive way to go up and down between the different suggestions when >> > > the >> > > tab key is being used for auto-complete. If that doesn't sound right >> > > we're >> > > open to ideas. >> >> > Thanks for the explanation. Now I agree that tab completion and >> > choosing from suggestions are different actions. I never had to cycle >> > through suggestions before I stumbled upon this issue. The problem was >> > that I got stuck at the top choice and completion didn't help to get >> > out, plus, the list of suggestions was rather odd. However, I >> > personally would prefer Ctrl+N/Ctrl+P instead of arrow keys. >> >> > So, I think the main issue is the list of suggestions, which seems >> > rather confusing sometimes. For instance, when I type 'g', the 'get >> > weather' is the top suggestion and Tab does not change anything, so >> > that I have only what I already typed in the command line. But when I >> > type 'ge', 'search with Ubuntu Package Search' (one of my search >> > engines) is on the top and Tab changes my 'ge' to 'Ubuntu Package >> > Search'. >> >> > > 2009/6/26 "mitcho (Michael 芳貴 Erlewine <[email protected]> >> >> > >> The tab completion is a feature we hope to keep, but unfortunately as >> > >> you've discovered it is only functioning in limited circumstances >> > >> right now. However, in my testing the tab completion of command names >> > >> only should be working. If this is not the case for you, I'd love to >> > >> know. If the first suggestion is not the right verb you want, you can >> > >> arrow down to the righ verb and tab that one. >> >> > >> mitcho (Michael Yoshitaka Erlewine) >> >> > >> On Jun 26, 2009, at 6:56 PM, Timur Izhbulatov <[email protected]> >> > >> wrote: >> >> > >> > Hi list, >> >> > >> > Recently I've updated to the latest 0.5 beta and noticed a very >> > >> > significant change in the command completion. >> >> > >> > Previously, to start a Google search I would just invoke Ubiquity, >> > >> > type 'goo' or even just 'go', then press Tab to complete the command, >> > >> > enter the query and press Enter. >> >> > >> > But now, even when I've already typed 'goo', the first item in the >> > >> > suggestions lists is 'add to google calendar' and I can't just press >> > >> > Tab to cycle over suggestions and choose 'google'. I'm forced to use >> > >> > arrow keys instead. >> >> > >> > In my opinion, this greatly reduces Ubiquity's usability and I would >> > >> > like to know if there is a way to change this behaviour. >> >> > >> > Thanks, >> > >> > -- >> > >> > Timur Izhbulatov ―www.timka.org >> >> > > -- >> > > Brandon James Pung >> > > Massachusetts Institute of Technology Class of 2010 >> > > Department of Electrical Engineering and Computer Science >> > > 828.777.8640 | [email protected] >> >> > -- >> > Timur Izhbulatov —www.timka.org > > > -- Timur Izhbulatov — www.timka.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
