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

Unable to paste ASCII escape character (ASCII #001B) #13857

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

Originally created by @htravis123 on GitHub (May 20, 2021).

Windows Terminal version (or Windows build number)

1.7.1033.0

Other Software

No response

Steps to reproduce

  1. Enter an SSH session to a Linux system.
  2. Copy and attempt to paste ASCII/Unicode character 0x001B, then CTRL+[.

Expected Behavior

The character ^[ should appear.

Actual Behavior

No character appears.

Originally created by @htravis123 on GitHub (May 20, 2021). ### Windows Terminal version (or Windows build number) 1.7.1033.0 ### Other Software _No response_ ### Steps to reproduce 1. Enter an SSH session to a Linux system. 2. Copy and attempt to paste ASCII/Unicode character 0x001B, then `CTRL+[`. ### Expected Behavior The character `^[` should appear. ### Actual Behavior No character appears.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:54:04 +00:00
claunia commented 2026-01-31 03:54:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 20, 2021):

This is by design as of #9034 -- we filter out control chars in pasted text so that rogue clipboard contents cannot break out of bracketed paste mode¹ or emit control sequences into the input stream.

What's your particular use case? We have a bindable sendInput action for sending raw data to the connected application that might be more suitable 😄, and if you're using an application that supports verbatim input (^V ^[) that may be an acceptable compromise.

¹ a safety and usability feature that allows an application to figure out when content came from the clipboard versus the keyboard

@DHowett commented on GitHub (May 20, 2021): This is by design as of #9034 -- we filter out control chars in pasted text so that rogue clipboard contents cannot break out of bracketed paste mode¹ or emit control sequences into the input stream. What's your particular use case? We have a bindable `sendInput` action for sending raw data to the connected application that might be more suitable :smile:, and if you're using an application that supports verbatim input (<kbd>^V ^[</kbd>) that may be an acceptable compromise. ¹ a safety and usability feature that allows an application to figure out when content came from the clipboard versus the keyboard
claunia commented 2026-01-31 03:54:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 20, 2021):

Here's the specific discussion about whether to filter always, or only when bracketing!

@DHowett commented on GitHub (May 20, 2021): [Here's the specific discussion about whether to filter always, or only when bracketing](https://github.com/microsoft/terminal/pull/9034#discussion_r571844024)!
claunia commented 2026-01-31 03:54:06 +00:00
Author
Owner
Copy Link

@htravis123 commented on GitHub (May 20, 2021):

I just tried to set a sendInput action for ESC+[, but it isn't working. Not sure if I am doing something wrong, though.

@htravis123 commented on GitHub (May 20, 2021): I just tried to set a sendInput action for ESC+[, but it isn't working. Not sure if I am doing something wrong, though.
claunia commented 2026-01-31 03:54:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 20, 2021):

Try this one-

{ "command": { "action": "sendInput", "input": "\u001b[" }, "keys": "whatever+you+want+for+keys" },
@DHowett commented on GitHub (May 20, 2021): Try this one- ``` { "command": { "action": "sendInput", "input": "\u001b[" }, "keys": "whatever+you+want+for+keys" }, ```
claunia commented 2026-01-31 03:54:07 +00:00
Author
Owner
Copy Link

@htravis123 commented on GitHub (May 20, 2021):

Actually, I didn't need the sendInput thingy, as I was already able to send ^[. but bash isn't accepting it as input.

@htravis123 commented on GitHub (May 20, 2021): Actually, I didn't need the sendInput thingy, as I was already able to send ^[. but bash isn't accepting it as input.
claunia commented 2026-01-31 03:54:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 20, 2021):

I don't think it's supposed to, unless you use verbatim input with ^V (you may need to unbind "paste" from ctrl+v to do that). Otherwise, it's going to expect a control sequence to follow the escape.

Verbatim input tells the connected application, if it implements it, that "the next character should be taken literally- do not attempt to parse it".

Here, I used ctrl+v, ctrl+[ to enter ^[ as a single character-

image

@DHowett commented on GitHub (May 20, 2021): I don't think it's supposed to, unless you use verbatim input with <kbd>^V</kbd> (you may need to unbind "paste" from `ctrl+v` to do that). Otherwise, it's going to expect a control sequence to follow the escape. Verbatim input tells the connected application, if it implements it, that "the next character should be taken literally- do not attempt to parse it". Here, I used <kbd>ctrl+v, ctrl+[</kbd> to enter `^[` as a single character- ![image](https://user-images.githubusercontent.com/189190/119026812-3498cb00-b96b-11eb-9da7-85640baea58a.png)
claunia commented 2026-01-31 03:54:08 +00:00
Author
Owner
Copy Link

@htravis123 commented on GitHub (May 20, 2021):

I don't think it's supposed to, unless you use verbatim input with ^V (you may need to unbind "paste" from ctrl+v to do that). Otherwise, it's going to expect a control sequence to follow the escape.

Verbatim input tells the connected application, if it implements it, that "the next character should be taken literally- do not attempt to parse it".

Here, I used ctrl+v, ctrl+[ to enter ^[ as a single character-

image

CTRL+V worked! Everything's in order. Closing issue.

@htravis123 commented on GitHub (May 20, 2021): > > > I don't think it's supposed to, unless you use verbatim input with ^V (you may need to unbind "paste" from `ctrl+v` to do that). Otherwise, it's going to expect a control sequence to follow the escape. > > Verbatim input tells the connected application, if it implements it, that "the next character should be taken literally- do not attempt to parse it". > > Here, I used ctrl+v, ctrl+[ to enter `^[` as a single character- > > ![image](https://user-images.githubusercontent.com/189190/119026812-3498cb00-b96b-11eb-9da7-85640baea58a.png) CTRL+V worked! Everything's in order. Closing issue.
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 Needs-Attention Needs-Tag-Fix Needs-Triage
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#13857
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?