starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

issue with control characters appearing in command window #9934

New Issue
Closed
opened 2026-01-31 02:07:54 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:07:54 +00:00
Owner
Copy Link

Originally created by @manbearian on GitHub (Jul 30, 2020).

suddenly my command window starting show control characters instead of doing the actions (e.g. image shows pushing the up arrow on the keyboard and then the down arrow). Other shells/tabs in the same terminal window don't have this issue.

image

Unfortunately i don't have a repro, and i don't know how i got into this state. I have a DMP of WIndowsTerminal.exe if that helps.

Originally created by @manbearian on GitHub (Jul 30, 2020). suddenly my command window starting show control characters instead of doing the actions (e.g. image shows pushing the up arrow on the keyboard and then the down arrow). Other shells/tabs in the same terminal window don't have this issue. ![image](https://user-images.githubusercontent.com/25087458/88950899-23e75f00-d24a-11ea-8e24-81d33d989ffd.png) Unfortunately i don't have a repro, and i don't know how i got into this state. I have a DMP of WIndowsTerminal.exe if that helps.
claunia added the Resolution-Duplicate label 2026-01-31 02:07:54 +00:00
claunia commented 2026-01-31 02:07:55 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 30, 2020):

So, this is usually caused by an application leaving ENABLE_VIRTUAL_TERMINAL_INPUT enabled when it exits. The input state is, unfortunately, global for a given console session (in Terminal, that's the tree of processes under one terminal pane)... which means applications can trivially mess with eachother like this.

@DHowett commented on GitHub (Jul 30, 2020): So, this is usually caused by an application leaving `ENABLE_VIRTUAL_TERMINAL_INPUT` enabled when it exits. The input state is, unfortunately, global for a given console session (in Terminal, that's the tree of processes under one terminal pane)... which means applications can trivially mess with eachother like this.
claunia commented 2026-01-31 02:07:55 +00:00
Author
Owner
Copy Link

@manbearian commented on GitHub (Jul 30, 2020):

thanks for the quick response; is there an manual fix i can run? i'd love to save this terminal session :)

@manbearian commented on GitHub (Jul 30, 2020): thanks for the quick response; is there an manual fix i can run? i'd love to save this terminal session :)
claunia commented 2026-01-31 02:07:55 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 30, 2020):

Hmm.. so, if you just run powershell and then exit it, it should restore the input mode. I just gave that a shot over here.

@DHowett commented on GitHub (Jul 30, 2020): Hmm.. so, if you just run `powershell` and then exit it, it should restore the input mode. I just gave that a shot over here.
claunia commented 2026-01-31 02:07:55 +00:00
Author
Owner
Copy Link

@manbearian commented on GitHub (Jul 30, 2020):

Btw, now that i can get my history for that shell, i believe that the culprit is vi. the last few previous commands were git diff invocations.

@manbearian commented on GitHub (Jul 30, 2020): Btw, now that i can get my history for that shell, i believe that the culprit is vi. the last few previous commands were `git diff` invocations.
claunia commented 2026-01-31 02:07:55 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 31, 2020):

Thanks for that! Yeah, it'll do that sometimes. Sorry 😄

For this one, by-design is appropriate, even though that's a little unfortunate. We're kicking around the idea of making the input mode per-process state, but our input queue is appalling right now. I tried to hack this up for hackathon!

/dup #4954

@DHowett commented on GitHub (Jul 31, 2020): Thanks for that! Yeah, it'll do that sometimes. Sorry :smile: For this one, by-design is appropriate, even though that's a little unfortunate. We're kicking around the idea of making the input mode per-process state, but our input queue is appalling right now. I tried to hack this up for hackathon! /dup #4954
claunia commented 2026-01-31 02:07:55 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 31, 2020):

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 (Jul 31, 2020): 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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9934
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?