After starting bash script encoding gliches #15723

Closed
opened 2026-01-31 04:46:36 +00:00 by claunia · 9 comments
Owner

Originally created by @NovaBG03 on GitHub (Oct 28, 2021).

Windows Terminal version (or Windows build number)

1.10.2714.0

Other Software

wsl2 ubuntu2004.exe
windows 11
bash

Steps to reproduce

when I start a bash script from github characters encoding glitches
image

Expected Behavior

To see the normal text
image

Actual Behavior

Encoding changes or idk what and I can't understand anything but if I type commands it works
image

Originally created by @NovaBG03 on GitHub (Oct 28, 2021). ### Windows Terminal version (or Windows build number) 1.10.2714.0 ### Other Software wsl2 ubuntu2004.exe windows 11 bash ### Steps to reproduce when I start a bash script from github characters encoding glitches ![image](https://user-images.githubusercontent.com/43469098/139186563-8a05fb45-1c36-4e90-b50f-a7f9e637787e.png) ### Expected Behavior To see the normal text ![image](https://user-images.githubusercontent.com/43469098/139186768-bb5a554b-e772-48f3-91ed-a79a039a2122.png) ### Actual Behavior Encoding changes or idk what and I can't understand anything but if I type commands it works ![image](https://user-images.githubusercontent.com/43469098/139186857-bb8e6102-168c-489a-8032-cf744f5f4bed.png)
claunia added the Resolution-Duplicate label 2026-01-31 04:46:36 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Oct 28, 2021):

start a bash script from github

Which script exactly?

This looks just like #11320

@zadjii-msft commented on GitHub (Oct 28, 2021): > start a bash script from github Which script exactly? This looks just like #11320
Author
Owner

@j4james commented on GitHub (Oct 28, 2021):

I would have thought this was more likely to be #10408. This is exactly what you'd expect to see if you've output an LS2 escape sequence (essentially printf '\en'). And if that's the case, you can get things back to normal by typing reset.

@j4james commented on GitHub (Oct 28, 2021): I would have thought this was more likely to be #10408. This is exactly what you'd expect to see if you've output an `LS2` escape sequence (essentially `printf '\en'`). And if that's the case, you can get things back to normal by typing `reset`.
Author
Owner

@DHowett commented on GitHub (Oct 28, 2021):

Yeah, this for sure looks like #10408. We'll need the script, to be sure.

@DHowett commented on GitHub (Oct 28, 2021): Yeah, this for sure looks like #10408. We'll need the script, to be sure.
Author
Owner

@NovaBG03 commented on GitHub (Oct 29, 2021):

reset fixed it but to run the command I need to cancel the script and then when I start it happens again

@NovaBG03 commented on GitHub (Oct 29, 2021): `reset` fixed it but to run the command I need to cancel the script and then when I start it happens again
Author
Owner

@DHowett commented on GitHub (Oct 29, 2021):

And do you happen to have the script available? It's difficult to diagnose precisely what's happening without that.

@DHowett commented on GitHub (Oct 29, 2021): And do you happen to have the script available? It's difficult to diagnose precisely what's happening without that.
Author
Owner

@NovaBG03 commented on GitHub (Oct 29, 2021):

I tried running printf '\en' and it glitched the encoding as well

@NovaBG03 commented on GitHub (Oct 29, 2021): I tried running `printf '\en'` and it glitched the encoding as well
Author
Owner

@DHowett commented on GitHub (Oct 29, 2021):

image

That script has a \en in it. It should not -- any mostly-compliant terminal should treat this as an escape sequence, even if it doesn't do anything.

@DHowett commented on GitHub (Oct 29, 2021): ![image](https://user-images.githubusercontent.com/189190/139479393-81fd8766-7443-4b8d-8488-79d35b53999c.png) That script has a `\en` in it. It should not -- any mostly-compliant terminal should treat this as an escape sequence, even if it doesn't do anything.
Author
Owner

@DHowett commented on GitHub (Oct 29, 2021):

/dup #10408.

@DHowett commented on GitHub (Oct 29, 2021): /dup #10408.
Author
Owner

@ghost commented on GitHub (Oct 29, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Oct 29, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15723