Skip to content

Intellisense stops working when stopped on a breakpoint #566

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

Closed
clmcgrath opened this issue Mar 16, 2017 · 4 comments
Closed

Intellisense stops working when stopped on a breakpoint #566

clmcgrath opened this issue Mar 16, 2017 · 4 comments
Labels
Issue-Bug A bug to squash.
Milestone

Comments

@clmcgrath
Copy link

clmcgrath commented Mar 16, 2017

System Details

  • Windows 10 1607
  • VS Code version: 3.10.9
  • PowerShell extension version: 0.10.0
  • Output from $PSVersionTable:
Name                           Value
----                           -----
PSVersion                      5.1.14393.693
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.693
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

Intellisense stops working when stopped on a breakpoint
if i am coding normally intellisense works as expected
if i set a breakpoint enter debug mode and try to write code i get no intellisense

Not Debugging

not-debugging

Debugging

debugging

Attached Logs

logs.zip
vscode-powershell.txt
EditorServices.txt
.

@daviwil
Copy link
Contributor

daviwil commented Mar 16, 2017

Thanks! I know what's causing this, will see if I can fix it quickly.

@daviwil daviwil modified the milestones: 0.10.2, 0.10.1 Mar 16, 2017
@daviwil daviwil added the Issue-Bug A bug to squash. label Mar 16, 2017
daviwil added a commit to daviwil/PowerShellEditorServices that referenced this issue Mar 16, 2017
This change adds IntelliSense (code completion) capabilities while the
debugger is stopped through invoking the TabCompletion2 command.

Resolves PowerShell/vscode-powershell#566.
@clmcgrath
Copy link
Author

@daviwil Looks like this is happening again since 0.11 was release looks like it is affecting the symbol search as well (ctrl-shift-o) now

doesn't give me the option to reopen the issue should I create a brand new one?

I will try and get you a new log on Monday morning or over the weekend if I am doing any coding at home

@daviwil
Copy link
Contributor

daviwil commented Mar 24, 2017

Hmmm, that shouldn't have been affected in this update. Definitely send along logs when you get a chance. I'll reopen this issue when I verify what's going on. Thanks!

@clmcgrath
Copy link
Author

clmcgrath commented Mar 29, 2017

@daviwil Ok, so it seems to be happening with long running commands not on a breakpoint
adding my logs from most recent session this happened in
vscode-powershell.txt
EditorServices.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

2 participants