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.
Errors in Powershell integrated console displayed "raw", not readable
See original GitHub issueOn one of my computers, when I run powershell code using VS Code, errors in integrated console are hardly readable.
It doesn’t seem parsed at all.
It look like this :
PS D:\SharePoint\_Git_Repos> d:\SharePoint\_Git_Repos\Sharepoint\Scripts\test.ps1 [91mfoo: [0mD:\SharePoint\_Git_Repos\Sharepoint\Scripts\test.ps1:1:1 [96mLine | [96m 1 | [0m [96mfoo[0m [96m | [91m ~~~ [91m[96m | [91mThe term 'foo' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was [96m | [91mincluded, verify that the path is correct and try again.
I think that happend after installing Powershell 7, but I’m not shure. I tryed to uninstall everything but Powershell with no luck.
Any ideas ?
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@TylerLeonhardt Just to clarify that this is not an exact duplicate. The missing of VT100 support affect the default error view in PS7. Updating on PSReadLine doesn’t help with it.
Still should leave this open because we should fix the issue where ErrorView is
concise.