No suggestions after typing new keyword
See original GitHub issueWhen typing the new
keyword no suggestions are shown. i.e. List<string> myList = new
at this point visual studio would suggestion completions.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:7 (2 by maintainers)
Top Results From Across the Web
VS Code Autocomplete not coming after typing a Keyword ...
My problem is that in VS Code after I type four particular keywords -> 'var', 'let', 'const', 'function', VS Code Intellisense for ...
Read more >Enable text suggestions in Windows - Microsoft Support
Enable text suggestions in Windows · Select (Start) > Settings. · In the Windows settings, select Time & language. · In the Time...
Read more >Use Autocompletions to suggest searches quickly
From the control panel, select the search engine you want to edit. Click Search features from the menu on the left and then...
Read more >Intellisense: Auto complete type after new keyword #809
Intellisense: Auto complete type after new keyword #809 ... Type is auto completed after the new keyword. Actual behavior. No auto complete.
Read more >Code completion | IntelliJ IDEA Documentation - JetBrains
For automatic completion enable the Show suggestions as you type option ... After the new keyword in an object declaration.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, there’s is some work yet to handle sorting. It’s getting much closer though! 😄 cc @rchande, who’s working on this as part of https://github.com/OmniSharp/omnisharp-vscode/issues/1765.
@DustinCampbell thanks for the progress on this
However I’m seeing this in v1.13.1
But I expected something like this