PowerShell/PowerShell

Set-PSDebug -Trace 1 prints only first line of a multiline command

Open

#8,113 opened on Oct 24, 2018

View on GitHubContributor guide
 (22 comments) (11 reactions) (0 assignees)C# (8,434 forks)batch import
HacktoberfestIn-PRUp-for-GrabsWG-Interactive-Debugging

Repository metrics

Stars
 (55,102 stars)
PR merge metrics
 (PR metrics pending)

Description

Steps to reproduce

Set-PSDebug -Trace 1

Write-Output "foo `
bar"

Expected behavior

Something like:

DEBUG:    3+  >>>> Write-Output "foo `
DEBUG:    4+  >>>> bar"

foo
bar

Actual behavior

DEBUG:    3+  >>>> Write-Output "foo `

foo
bar

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.2.0-preview.1
PSEdition                      Core
GitCommitId                    6.2.0-preview.1
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Contributor guide

Research direction
Investigate the Set PSDebug trace implementation to handle multiline commands properly.
Tech stack
shell
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PowerShell basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60