what if I want to search for something with a comma in it?
Rules for Autocomplete
141–150 of 151 posts
Re: Rules for Autocomplete
#142Here's two autocomplete mistakes that really irritate me: - Autocomplete on enter: Chrome does this, if I type in https://example.com (enter), it makes the mistake of autocompleting to https://example.com/some_page_I_visited_yesterday - Arguing: Some applications that I use have autocomplete spell checkers that continue to aggressively try to "correct" technical terms, uncommon names, or company jargon that's not kno…
I do a double space when I want to goto an exact match of what I typed.
Re: Rules for Autocomplete
#143Earlier quoted context omitted.
Unlearning is a great option. I have in Firefox a persistent autocompletion for a URL that I typo'd once, which still shows before the one I've been to a thousand times (because it's first alphabetically, I suppose?)
My biggest gripe with Firefox's history bar is that it's so slow to update that I'll go to click something, and then the whole list scrolls down or up and I now click something entirely different. Even with search autocomplete disabled it takes forever just to search the history.
[deleted]
Re: Rules for Autocomplete
#144Earlier quoted context omitted.
Holding down on the word in the auto compete will allow you to delete it from your dictionary.
Thanks! Didn't know that. Another annoyance that, while not the fault of autocomplete, still bothers me: I write in either Spanish or English, frequently changing between the two. It's hard to explain, but the UX of swiping right to change the keyboards generates too much friction on my brain when I'm tired (like when commuting back from work), so I end up using the Spanish default even when writing in English. There…
[deleted]
Re: Rules for Autocomplete
#145Earlier quoted context omitted.
Unlearning is a great option. I have in Firefox a persistent autocompletion for a URL that I typo'd once, which still shows before the one I've been to a thousand times (because it's first alphabetically, I suppose?)
You can use Shift+Delete on an entry to remove it from the autocomplete list.
Not easily on a Mocbook Pro, which doesn't have a Delete key. Shift+Backspace doesn't work.
Re: Rules for Autocomplete
#146The biggest autocomplete annoyance I find in some implementations is that they spring into action the moment you type a single character, and then do so much processing (in apparently the same thread) that they horribly slow down the entry of subsequent characters! You make mistakes due to the lag, and the whole experience is just shit. The run prompt in Microsoft Windows is like this.
Like, hold your horses for three or four seconds so I can type more, then you have less to search for. Prioritize my typing response time over the background search, damn it!
(Really, explicit auto-complete is best, like in command lines ("Tab completion")).
The second biggest gripe is autocomplete choices that dispatch the command. Sometimes you see an autocomplete item that is close to what you want, except for a small edit or addition. Nope, you can't just have that completion in your edit buffer for further refinement: that item is actually just an item in a dynamically constructed pop-up menu, bound to do the dispatch action.
Third gripe: caching invalid entries, such as misspellings, and offering them in future auto-completions! Browsers do this: you misspelled a domain name three weeks ago, so the resulting URL couldn't possibly load, but now it's still coming up as a completion item!
Re: Rules for Autocomplete
#147Earlier quoted context omitted.
I see no reason this doesn’t work for Lon and Lond and London. It turns out that people in London, England have to type 2 more letters, a task that I am sure is not beyond them.
> It turns out that people in London, England Together with all the other millions of people that write London around the world. According to google trends London is searched about 20-30 times more often than Lon. Sorting Lon before London (in absence of more information) seems a bad choice.
And I wonder how much the Lon search results are inflated by this same phenomenon? It may be a lot worse than 20-30 times.
Re: Rules for Autocomplete
#148Earlier quoted context omitted.
You can use Shift+Delete on an entry to remove it from the autocomplete list.
Not easily on a Mocbook Pro, which doesn't have a Delete key. Shift+Backspace doesn't work.
Really? I have a five-year-old MBP with a key labeled "Delete" (although it really seems to be "Backspace").
Re: Rules for Autocomplete
#149Earlier quoted context omitted.
You can use Shift+Delete on an entry to remove it from the autocomplete list.
Not easily on a Mocbook Pro, which doesn't have a Delete key. Shift+Backspace doesn't work.
On MacBooks the combination of Fn+Backspace mimics Delete. So Shift+Fn+Backspace to remove a suggestion.
Re: Rules for Autocomplete
#150Here's two autocomplete mistakes that really irritate me: - Autocomplete on enter: Chrome does this, if I type in https://example.com (enter), it makes the mistake of autocompleting to https://example.com/some_page_I_visited_yesterday - Arguing: Some applications that I use have autocomplete spell checkers that continue to aggressively try to "correct" technical terms, uncommon names, or company jargon that's not kno…
MacOS Mail has the worst autocomplete feature I've ever seen when it comes to the "To:" field. When I have to manually type a new e-mail address, it always selects some other e-mail address. I've just tried again: return validates the wrong address, tab does the same, clicking elsewhere does the same... A complete nightmare!