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

Bash fails to pass control characters to cmd.exe #62

New Issue
Closed
opened 2026-01-30 21:41:03 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:41:03 +00:00
Owner
Copy Link

Originally created by @skylize on GitHub (Jan 30, 2018).

Windows build number

10.0.17074.1002

What you're doing and what's happening

In Windows WSL Bash Terminal

  1. Open cmd inside the Bash terminal and type any command.
sky@SkyZen:~$ cmd.exe
Microsoft Windows [Version 10.0.17074.1002]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>echo hello
echo hello
hello
  1. Press ↑.

What's wrong / what should be happening instead

Actual behavior: A textual representation of the Up Arrow control key gets typed into the input field.

C:\WINDOWS\system32>^[[A

Expected behavior: Pressing ↑ will show the previous command in the input field.

C:\WINDOWS\system32>echo hello
Originally created by @skylize on GitHub (Jan 30, 2018). ### Windows build number 10.0.17074.1002 ### What you're doing and what's happening In Windows WSL Bash Terminal 1. Open `cmd` inside the Bash terminal and type any command. ``` sky@SkyZen:~$ cmd.exe Microsoft Windows [Version 10.0.17074.1002] (c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>echo hello echo hello hello ``` 2. Press <kbd>&uparrow;</kbd>. ### What's wrong / what should be happening instead ***Actual behavior***: A textual representation of the Up Arrow control key gets typed into the input field. ``` C:\WINDOWS\system32>^[[A ``` ***Expected behavior***: Pressing <kbd>&uparrow;</kbd> will show the previous command in the input field. ``` C:\WINDOWS\system32>echo hello ```
claunia added the Product-ConhostProduct-WSL labels 2026-01-30 21:41:03 +00:00
claunia commented 2026-01-30 21:41:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 1, 2018):

Yea, interactive interop is pretty wonky in WSL currently. There's a myriad of issues about it filed over at the WSL repo. I'm sure this could be duped to one of those issues.

@benhillis for visibility.

@zadjii-msft commented on GitHub (Feb 1, 2018): Yea, interactive interop is pretty wonky in WSL currently. There's a myriad of issues about it filed over at the [WSL repo](https://github.com/microsoft/WSL). I'm sure this could be duped to one of those issues. @benhillis for visibility.
claunia commented 2026-01-30 21:41:05 +00:00
Author
Owner
Copy Link

@bpsib commented on GitHub (Oct 3, 2018):

The arrow keys worked as expectedly on cmd.exe when I tried on insider build 17744 so this may be fixed.

@bpsib commented on GitHub (Oct 3, 2018): The arrow keys worked as expectedly on cmd.exe when I tried on insider build 17744 so this may be fixed.
claunia commented 2026-01-30 21:41:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 3, 2018):

There's been a significant amount of change in WSL->Win32 interop, specifically around console applications, since build 17074. This is almost certainly fixed. Thanks!

@DHowett-MSFT commented on GitHub (Oct 3, 2018): There's been a significant amount of change in WSL->Win32 interop, specifically around console applications, since build 17074. This is almost certainly fixed. Thanks!
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 Product-Conhost Product-WSL
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#62
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?