Terminal in VSCode Insiders not able to display special characters #211922
Comments
Tyriar
added
bug
|
@GBoGH can you share your starship.toml? Also are you using Windows PowerShell (powershell.exe) or pwsh 6+? Could you get the version of that via |
|
Same issue for us using bash 5.0.17(1) so might not be pwsh dependent. Terminal prompt now not showing special characters on latest insiders update 1.90.0 e.g. \x1b[01\x3b34m~/code/project1\x1b[00m (main))$ ~/code/project1 (main))$ |
|
Where can i get the starship.toml? |
|
I have the same exact problem, and the following suggestion finally fixed it on my end: #212130 (comment) |
|
I agree, the instructions could have been clearer. The commit selection does seem a bit random, but what I did was clicking 'Browse files' on the commit and found the |
|
It was pushed to the official build. I'm having this issue and I dont rememeber ever joining any kind of insider program. |
VSCodeTriageBot
removed
the
insiders-released
|
To verify:
|
|
Same issue here. oh-my-posh, powershell, issue only with vscode, windows term looks as intended. |
|
This should be fixed in v1.90.2 which was just released |
|
Can confirm as fixed. Thanks for the work! |
|
confirm as fixed and work well without needing to disable
|
|
Looks good again! |
|
Looks good to me too!! |
|
This morning, I updated my VS Code, activated the
|
|
Still same issue |
|
@martindotpy what shell/prompt is that? |
|
@Tyriar It's the PowerShell from the Microsoft Store. Special characters appear when I press Ctrl + L to clear the terminal. I also have the same problem in Git Bash, but it happens when I execute a command. In both cases, I am using Oh My Posh.
|
|
I was also having a related? problem with PowerShell integration since the 1.90 release. The recent 1.90.2 update has changed the outcome a little, but not fixed it. I get output like the below when I open a new pwsh terminal, and often the terminal stops responding after executing a command or two. I have this PowerShell profile. I thought any of PSFzf, zoxide, or the encoding settings could be the culprit, so I tried removing each one. Oddly, removing any combination of them doesn't fix the problem, but completely blanking out the file fixes it (second image below). It all worked fine in vscode prior to 1.90. # UTF-8 encoding!
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()
# environment
$Env:FZF_DEFAULT_COMMAND = 'fd --type file --color=always --follow --hidden --exclude .git'
$Env:FZF_DEFAULT_OPTS = '--ansi --layout=reverse --height 40%'
# PSFzf
Remove-PSReadlineKeyHandler 'Ctrl+r'
Import-Module PSFzf
# zoxide
if (Get-Command "zoxide" -ErrorAction Ignore) {
Invoke-Expression (& { (zoxide init powershell | Out-String) })
}
|
|
@wjrogers you have the experimental suggest setting enabled, disabling that will fix it. What version of PowerShell is that you're using? Currently in Insiders we force suggest to be disabled on Windows PowerShell (5), but if you're experiencing it in a latter version maybe we need to disable it in older versions of Windows too. |
@Tyriar Are you referring to a different setting?
|
|
@Tyriar OOPS, I did have an old version of that setting in my {
"terminal.integrated.shellIntegration.suggestEnabled": true
} |
|
Is there a separate issue tracking this behavior with
The workaround of invoking |
and others
Type: Bug
The terminal in VSCode - insiders is unable to display special characters in terminals after latest update
How it looks in VSCode:
How it looks in VSCode - insiders
The font settings are the exact same for both versions
VS Code version: Code - Insiders 1.90.0-insider (a1f2ea3, 2024-05-03T05:49:15.006Z)
OS version: Windows_NT x64 10.0.22631
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Extensions (40)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: