Debugger operations should print out the action that was taken in Integrated Terminal

[pcgeek86]

System Details

• Operating system name and version:
• VS Code version:
• PowerShell extension version:
• Output from $PSVersionTable:

Copy / paste the below commands into the PowerShell Integrated Terminal, and paste the output here

PS C:\> code -v
1.10.2
8076a19fdcab7e1fc1707952d652f0bb6c6db331
PS C:\> $pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
0      12     0      0

PS C:\> code --list-extensions --show-versions
ms-vscode.PowerShell@0.12.1

PS C:\> $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

When stepping through the debugger, a new line is printed in the Integrated Terminal each time a debugger action is taken (eg. Step Into, Step Out, etc.), showing the PowerShell prompt. This could be improved to be more useful by showing the debugger action that was taken each time a new line is printed, instead of showing just the prompt by itself.

Low priority.

Cheers,
Trevor Sullivan

[daviwil]

Good idea!

[rkeithhill]

@pcgeek86 Are you sure about this? I'm already finding it a bit annoying that my output is scattered all over the place in the integrate console e.g.:

Why can't the output be like this:

I don't see much value is seeing a bunch of lines that say step over, step over, step into, step, ... ? And why are getting a blank line spit out to the integrated console whenever we step over a line that generates no output? OK, now you all can come back on my lawn. :-)

BTW I don't mind seeing a line that tells me why the output stopped (hit breakpoint) but that's about the limit for me.

[daviwil]

@rkeithhill are you stepping through the script? What's your prompt function? It should be writing out your prompt each time the debugger stops:

My prompt returns a > so that's why it looks like this.

[rkeithhill]

There is an error in my prompt function at the moment. I'm using my branch of an ANSI-ized posh-git and I introduced an error the other night that I need to fix. However, in the regular console, if the prompt function errors out, it supplies a simple PS> prompt. Maybe we should do something similar here. Either > or PS>.

[rkeithhill]

OK, actually the problem was I switched to a branch that used an incompatible GitPromptSetting. Anyway, this is better (I think). Might need to rethink by DBG prompt - make it a single line:

[daviwil]

It used to do that but I think I broke it when I changed how I gather the prompt. I'll try to fix that for 0.13.0.

[pcgeek86]

Here's what I'm seeing when kicking off debugger commands. One line per debugger task, but only the prompt is shown. It would be more useful to actually see the individual debugger tasks that were invoked (think Get-History, but for the debugger interface).