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

[htravis123]

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.

[DHowett]

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]

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

[htravis123]

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

[DHowett]

Try this one-

{ "command": { "action": "sendInput", "input": "\u001b[" }, "keys": "whatever+you+want+for+keys" },

[htravis123]

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

[DHowett]

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-

[htravis123]

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-

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