Skip to content

shellIntegrationAddon.ts: only decode messages for VSCodeOScPt, not iTerm2 - #165579

Merged
Daniel Imms (Tyriar) merged 2 commits into
microsoft:mainfrom
rwe:shellint-no-decode-iterm2
Nov 23, 2022
Merged

Daniel Imms (Tyriar) merged 2 commits into
microsoft:mainfrom
rwe:shellint-no-decode-iterm2

Conversation

@rwe

Copy link
Copy Markdown
Contributor

Unlike VSCodeOscPt.Property, the iTerm2 OSC sequences do not support backslash or hex-escape sequences. Interpretation of those messages should not attempt evaluation of those escapes.

See: https://github.com/gnachman/iTerm2/blob/bb0882332cec5196e4de4a4225978d746e935279/sources/VT100Terminal.m#L2089-L2105

@Tyriar Daniel Imms (Tyriar) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Tyriar Daniel Imms (Tyriar) added this to the November 2022 milestone Nov 23, 2022
@Tyriar
Daniel Imms (Tyriar) merged commit 33671e4 into microsoft:main Nov 23, 2022
@rwe
Robert Estelle (rwe) deleted the shellint-no-decode-iterm2 branch November 23, 2022 18:18
@github-actions github-actions Bot locked and limited conversation to collaborators Jan 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants