You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ANSI codes appearing as autocomplete visual artifacting #1558
Visual Studio Code implements its own terminal for everything using xterm.js. It's also cross-platform so I don't think they can integrate a Windows-only component.
Thanks for reporting the issue. The issue has been fixed in the master branch (#1496), by making the predictive suggestion feature off by default. The predictive suggestion feature can be turned on by Set-PSReadLineOption -PredictionSource History (by default the PredictionSource is None). But if PSReadLine is used in a host that doesn't support VT100, that feature cannot be enabled -- Set-PSReadLineOption -PredictionSource History will throw error accordingly.
Activity
gilescope commentedon May 29, 2020
I wonder if you can integrate windows terminal into vscode because that’s the true fix for ansi codes appearing.
Sent with GitHawk
vexx32 commentedon May 29, 2020
Visual Studio Code implements its own terminal for everything using xterm.js. It's also cross-platform so I don't think they can integrate a Windows-only component.
SeeminglyScience commentedon May 29, 2020
If they were running a build of Windows that could install terminal (they appear to be running server 2k12), the escape codes would work fine anyway.
iirc PSReadLine has a check for when the OS doesn't support ANSI escapes and should revert to a simplier renderer.
Some possibilities:
I never really looked at the code for the simple interface so some of the above might be nonsensical.
daxian-dbw commentedon Jun 4, 2020
Thanks for reporting the issue. The issue has been fixed in the master branch (#1496), by making the predictive suggestion feature off by default. The predictive suggestion feature can be turned on by
Set-PSReadLineOption -PredictionSource History(by default thePredictionSourceisNone). But if PSReadLine is used in a host that doesn't support VT100, that feature cannot be enabled --Set-PSReadLineOption -PredictionSource Historywill throw error accordingly.