Default all G-sets to ASCII unless ISO-2022 is requested (was: Terminal breaks on \x1b O) #14208

Open
opened 2026-01-31 04:03:50 +00:00 by claunia · 0 comments
Owner

Originally created by @iamdbychkov on GitHub (Jun 11, 2021).

Windows Terminal version (or Windows build number)

1.8.1521.0

Other Software

OpenSSH_5.3p1

Steps to reproduce

  1. SSH to linux server (for me it's CentOS, if it matters)
  2. echo -e '\x1bo'

Expected Behavior

I expect that terminal will continue to work properly

Actual Behavior

I can no longer type "actual" text in terminal, every key press transforms in a mess seen on screenshot. CTRL+Something sequences are also no longer working.

изображение

Stumbled upon this issue when I was debugging gsm7 encodings in python program (\x1b is a common byte for this encoding). On yet another 'print()' terminal became a mess.

Issue is not reproduced if i'm using powershell.exe or cmd.exe without it being embeded in WT.

Originally created by @iamdbychkov on GitHub (Jun 11, 2021). ### Windows Terminal version (or Windows build number) 1.8.1521.0 ### Other Software OpenSSH_5.3p1 ### Steps to reproduce 1. SSH to linux server (for me it's CentOS, if it matters) 2. `echo -e '\x1bo'` ### Expected Behavior I expect that terminal will continue to work properly ### Actual Behavior I can no longer type "actual" text in terminal, every key press transforms in a mess seen on screenshot. CTRL+Something sequences are also no longer working. ![изображение](https://user-images.githubusercontent.com/53076075/121656464-2c363a80-caa8-11eb-9afa-4dbc3209debf.png) Stumbled upon this issue when I was debugging gsm7 encodings in python program (\x1b is a common byte for this encoding). On yet another 'print()' terminal became a mess. Issue is not reproduced if i'm using powershell.exe or cmd.exe without it being embeded in WT.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14208