-
Notifications
You must be signed in to change notification settings - Fork 510
IntelliSense broken #2253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The particular syntax you're using there isn't valid PowerShell; a function can take a param block or it can take a parameter list in parens, but not How about something like: In this case though, you're still in an empty file and most of what you're writing are either keywords or parameter names. We get our completions from PowerShell and it doesn't provide keyword completions. Nor does it provide parameter name suggestions or untyped hashtable key/value suggestions. Basically, in the scenario you've got, things are still wide open, so there are no completions to provide. Do you get completions on |
To me it looks like there is some random condition that's keeping PowerShell IntelliSense from providing results in a timely manner. Look at this screencast I just recorded: Typing Then, after deleting my line, hitting |
Yes, this is a performance issue in the current stable PowerShell extension. It's improved in the preview extension, and we think the next release of the preview extension will have significant improvements here. You can try the preview extension by uninstalling the We've also committed to getting these improvements into the stable channel in January, so this should be improved over the course of the next few months. |
Going to mark this as a duplicate of #647 |
This issue has been marked as duplicate and has not had any activity for 1 day. It has been closed for housekeeping purposes. |
Issue Description
I am experiencing a problem with IntelliSense. It doesn't auto-complete whatsoever:
Attached Logs
Follow the instructions in the README about capturing and sending logs.
The link points to no README (404).
EditorService.log
vscode-powershell.log
Environment Information
Visual Studio Code
PowerShell Information
Visual Studio Code Extensions
Visual Studio Code Extensions(Click to Expand)
The text was updated successfully, but these errors were encountered: