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
VS Code's terminal has started to eat unicode #110506
Comments
Are you using VS Code in a remote workspace? (for example, using the Remote-SSH, Remote-Containers, or Remote-WSL extensions) |
Also, can you try running
I don't know a ton about this but it seems like your hex dumps would show that fish is just not sending those characters in the vscode terminal environment, right? And a third question - your post shows that you are on version 1.50, we have released 1.51, is that because you downgraded after seeing this issue, or have you not yet updated to 1.51? |
I'm not using any of those extensions. AFAIK this is native. Yeah I can run that. Tbh I'm not quite sure what's happening.
I'm on 1.50 because Arch hasn't updated to 1.51 yet. |
Does it work if you switch to bash or sh? |
Sorry for the delay. I was installing shellder on zsh. And it displays the glyphs fine. (Note the glyphs aren't displaying correctly on GitHub.)
Sorry in light of this it may not be a VS Code issue. Since fish didn't update it seems like a bug's came out of no-where. |
Found the problem. If I use |
Does this issue occur when all extensions are disabled?: Yes
I updated VS Code yesterday and now I'm getting missing glyphs in my prompt. These worked fine before the update.
Steps to Reproduce:
Install fish
Install oh-my-fish
Install shellder
Open VS Code
Here is a comparison of the hex output that VS Code's terminal, kitty and xterm produce. I typed
exit
to exit fish in each. I also have a preview of what this looks like in each terminal.VS Code
Full hexdump
kitty
Full hexdump
xterm
Full hexdump
We can see some differences in the ANSI escape codes. However the core of the prompt are the same. I have padded the
?
to make this easier to see.I have also made the hex easier to compare. This is the hex for the above and we can see VS Code is eating the ee82b0 and ee82a0. The output for this section between xterm and kitty is again identical.
Please can I have the Unicode in my prompt back.
The text was updated successfully, but these errors were encountered: