-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Integrated terminal does not line wrap when prompt string contains emojis #44340
Comments
(Experimental duplicate detection) |
@martypdx can you share your $PS1 variable? Run |
📂 rehype-add-classes 🚀 echo $PS1
📂 \W 🚀 |
It's the pictorial unicode 📂 🚀 |
@martypdx does this happen in an external terminal when the width is set the same? It looks like all the terminal is doing here is following instructions from bash, and bash is not saying to go the next line. |
@Tyriar works fine in external terminal. Worked in prior release of VSCode. |
@martypdx hmm, maybe the shell thinks it's wider than the terminal for some reason then? If you keep typing will it eventually wrap? Also you could try test it in Insiders as a lot has changed with regards to layout in the terminal since 1.20 due to the introduction of splitting. https://code.visualstudio.com/insiders/ |
Yes, the second time around it wraps and subsequent lines wrap correct.
Problem still exists in Insiders :(
But it only happens with certain characters in $PS1. Perhaps it's checking for certain character ranges and it needs to be broadened? |
I now there's an issue with emojis right now if you add one to the prompt and delete it, this could be related to that? |
@Tyriar Yeah, looks like if you paste an emoji and then hit backspace/delete it removes two characters. I have seen other off-by-one behavior like this as well. |
This is a bug in https://github.com/xtermjs/xterm.js, I don't think there's a tracking issue currently. |
The original report where there is an issue with wrapping I believe is a problem with bash. For backspace this is tracked in xtermjs/xterm.js#1059 |
This started with latest release
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: