code-completion doesn't use next suggestion on pressing tab multiple times

[DomiR]

TL;DR the tab key should insert first suggestion, but then cycle through suggestions, replacing the last completion.

Sublime autocompletion can be configured so that when pressing the tab multiple times it will cycle through the autocompletions by inserting the first suggestion (closing the suggestion box), then replacing the suggestion by succeeding ones when pressing tab repeatedly.

Problem description:
Visually:

// e.g. 1. typing`whatI` will render both options in suggestion box
whatI|
      -whatIGet   // => 2. first option will be autocompleted on `tab` closing the suggestion box
      -whatIWant // => 3. on second `tab` this should replace the first (wrong) suggestion

function whatIWant() {}

funciton whatIGet() {}

Textually:

1. Type whatI
2. Suggestions will pop up
3. Wrong suggestion is highlighted
4. tab to complete wrong suggestion
5. Suggestions-popup disappears
6. Still at the end of inserted suggestion press tab again
7. Wrong suggestion should be replaced by next suggestion in list

Currently the corresponding controllers don't seem to support this, as accepting the current suggestion to my understanding will clear the suggestion list.

https://github.com/Microsoft/vscode/blob/3215f19074d49e32d5ab55203923865910d4d5ca/src/vs/editor/contrib/suggest/browser/suggestController.ts
https://github.com/Microsoft/vscode/blob/794b435b27bcf4a92cc0a6345b97821e3c827dcc/src/vs/editor/contrib/suggest/browser/suggestWidget.ts

How are people getting around having to press arrow-down and arrow-up 🤦‍♂️? I somehow never get the correct suggestion at the top and I quite frankly don't have the most flexible pinky 😢

[andreyorst]

4. tab to complete wrong suggestion
5. Suggestions-popup disappears

Yeah, but why close popup on tab?

If your correct suggestion isn't next in the list, and popup is closed you can run into a situation when you rapidly pressed tab key and gone too far in your list, then you could use ↑ to go up, but there is no popup so you wil probably change line.
Yes, I know that you can use shift+tab to go backwards in the list, but I think it is better to see list, because it is changing all the time, and you dont need to remember how far your suggestion is.

Well maybe someone dont like the fact that when completion is done, no matter wrong or right one, the list is still there and hovers above the code, hiding it from eyesight, and closing popup after first tab is good for them, but there are other people like me who like the opposite behavior, when the popup is always open until you close it by typing. So there may be an extra option for popup behavior

[Naramsim]

A nice GIF showing what we can do in Sublime

https://stackoverflow.com/questions/48883721/cycle-to-previous-suggestions-in-vscode

[ryanflorence]

This isn't exactly a duplicate of #34694, supertab in vim keeps the popup open, and doesn't pop up until you hit tab.

Code completion the way VSCode handles it is really disruptive and slower than just typing out what I want :\

[andreyorst]

@ryanflorence well, the main idea of any modern autocompletion system is fuzziness. Thats is, you don't need to scroll through list most of the time. Let me demonstrate this:

At first I typed sii wich gave me some_function_with_name_that_is_not_shorter()
And then I type sul and got some_function__that_has_unnecessary_long_name()

However it is not always possible to match with fuzzy, like here:

(Imagine that I need that int variable)
and therefore I likely need to spam a tab key some times (I actually use vim with deoplete, so I can), but again, usually I don't, because like here, it is faster to hit c twice.

BTW not regarding to topic, why supertab? It's not nearly as good as standard vim completion system, and far behind other async plugins like deoplete or neovim-completion-manager, or even that bloated YCM

[davidnorthetal]

@andreyorst fuzzy searches are not orthogonal to cycling and I'm quite sure everyone here understands how fuzzy searches work

you fuzzy-search when you know the symbol you're looking for (or have a strong suspicion) but don't want to write it all out yourself
you cycle when you want to explore your options

this issue isn't about fuzzy-searches however, it is about triggering autocomp and cycling, so let's stay ontopic

[andreyorst]

so let's stay ontopic

ok, you want cycling. I'm not against cycling either. Let me explain myself. I'm against programmers who cycle around after every keypress, browsing kilometers of completion items, just to get single one, wich they even know about, but just because it's so fun to cycle around they will do it. In most cases you need to press one extra key (rarely two) to fuzzy match through hell lot of items in the list, but they will hold Tab and wait until chooser will reach their desired completion item. Thats why vscode completion system is good. It disciplines programmer to use his brain instead of brute force. It is hard to figure out how much more productive you will be if you will not scroll every time, and fuzzy match through.

However cycling may benefit in some cases, when you have to deal with messed codebase, with large classes with tons of fields and methods, and you just want to examine it. The problem is only the fact that arrows used for that.