Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
get-history | Out-ConsoleGridView with multi-line commands causes issues
See original GitHub issueStart with:
$someJson = @'
{
"foo" : true
}
'@
Then
get-history | Out-ConsoleGridView
Results in something ugly like this:
Powershell 7.0.
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
How to end a multi-line command in PowerShell
It is talking about splitting a command over multiple lines and all the answers are about using a backtick to escape the line...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Got it. Found https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_special_characters?view=powershell-7
I think following PowerShell syntax, it may make more sense to replace
\nwith`n. Otherwise, this seems like a good improvement.