Inconsistencies with Trigger (full) completions when (incomplete) completions are already active

• VSCode Version: 1.49.3
• OS Version: 10.15.7

@jrieken

This is a follow up to https://github.com/microsoft/vscode/issues/99504. The issue is fixed in some instances, but not in others.

Here’s an example with a Go file where I have space enabled as a trigger char and then retype the line with space disabled as a trigger character.

Previously, upon typing return n, only Kite’s completions would display. This has since been fixed via #99504. But, you can see in the gif that return nil, e results in Intellisense completions being suppressed, unless the trigger for space is turned off.

Similarly for JS:

Previously, IntelliSense completions for setAutoInstallPluginsEnabled: (e were being suppressed. This has since been fixed. But, setAutoInstallPluginsEnabled: (enabled) => dis results in completions being suppressed. If I turn off space as a trigger, VSCode is able to suggest dispatch and disabled, as you can see at the end of the screen capture.

[jrieken]

Yeah, that would work

[edzkite]

@jrieken Thanks for looking into this. If I understand you correctly, what you’re saying is that we’re triggering completions outside of a word (AKA anything alphanumeric separated by spaces), which breaks “triggering into the next word”.

What’s not possible is to re-start when entering a word no matter if a proceeding word exists. That would break things like member completion after .

I’m not quite sure I follow the implications of this 100%. Could you expand on that?