-
Notifications
You must be signed in to change notification settings - Fork 511
ANSI Escape Code received from the SSH from the Linux's BASH breaks the output in the PowerShell Integrated Console #3543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, while Code won't recognize and highlight it, it's a valid option and enables tracer logs on the server. Please enable this setting and provide these logs. Thanks! |
If this is empty it means you're executing in a regular |
…3544) Add this additional note as VS Code does not recognize this setting. The result is: 'Unknown Configuration Setting'. #3543 (comment)
Could you try getting the output of |
Oh I thought you were on linux my bad, not related then. Might be console mode related. There isn't really a quick way to test that like there is for stty though afaik |
Can you confirm this is still reproducing with v2021.9.0? I mean, it probably does, but it'd be helpful to know. Otherwise we're hoping the editor services pipeline work (PowerShell/PowerShellEditorServices#1295) may fix it as it replaces much of our custom console host implementation with re-use of PowerShell's own (which clearly works). |
Thought so. We'll have to try to repro it, but also are hopeful the work Rob is doing may fix it. Unfortunately these kinds of issues tend to be the most difficult to fix. |
Hello, and thank you for your patience! The latest PowerShell Preview for VS Code is now out, and includes the reworking of our pipeline and threading architecture in PowerShell/PowerShellEditorServices#1295. Could you verify if this issue still reproduces using v2021.10.3-preview? Please note that this preview is likely to include other bugs, and you should feel free to file new issues for those so we can work through them. Thanks again! |
Awesome!! |
This issue has been marked as fixed. It has been automatically closed for housekeeping purposes. |
.
The text was updated successfully, but these errors were encountered: