Vim: <C-n> doesn't work as expected

[parthsharma1996]

Describe the bug
The native vim auto-complete doesn't seem to work. Therefore, I am not seeing auto-complete in things like strings

To Reproduce
Steps to reproduce the behavior:

1. Initialize a long string into a variable
2. Try to use that variable again somewhere, auto-complete window pops up.
3. Try to use that string again somewhere and attempt auto-complete by pressing
4. No auto-complete suggestions show up

Expected behavior
I should get an auto-complete prompt to complete that long string.

Screenshots

1. 
   
   2,

3.

Environment :

• Extension (VsCodeVim) version: 0.16.6
• VSCode version: 1.27.2
• OS: Arch Linux

[laktak]

Same here. The readme should mention if this is not supported.

[jcredland]

This is one of my favourite VIM features and it's sorely missed. Any chance it could be added ?

[jcredland]

Just to add: not only is this useful for auto-completing in strings, its great for creating variable definitions from words in comments, auto-completing in comments when writing documentation etc. etc.

[J-Fields]

VSCode has auto-complete, which is powered by LSP only, I think. It doesn't seem like the responsibility of a vim emulation layer to act as a language server, just feeding VSCode back the document split into words. This issue hasn't gained much traction and I don't see it as realistic, so I'm closing the ticket. Let me know if you object.

[emergy]

really lacking this feature. Tell me how to emulate it

[J-Fields]

@emergy As I stated above, because VSCode is driven by LSP, I don't see a reasonable way to provide autocomplete for things like string literals. If the lack of this feature is a deal-breaker, you can use terminal vim or a GUI driven by neovim's API (such as Oni).

[J-Fields]

Or, if someone wants to prove me wrong, they can write up a proof of concept and send me a PR.