PowerShell / PowerShell/vscode-powershell

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

Open
#652 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Debugging Issue-Discussion Issue-Enhancement
Dominant language
TypeScript
Stars
1.9k
Forks
547
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the debugger action handling and the Integrated Terminal output path, focusing on how Step Into, Step Out, and similar actions produce a new prompt line. Confirm the terminal can identify the action taken, then verify that each debugger operation prints its action instead of only the prompt.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, typescript, vscode
Domain
developer-experience, devtools
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.