-
Notifications
You must be signed in to change notification settings - Fork 9k
Fix another VT input double-encoding issue #19083
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
26e4e4c to
5c06ff4
Compare
|
@j4james You wrote:
I believe we don't need to care about this, because the VT parser already detects control characters and F-key input sequences, etc., and calls |
DHowett
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this have a negative impact on hosting terminals which do not use mode 9001, talking to applications which use ENABLE_VIRTUAL_TERMINAL_INPUT?
|
How do I get a daily build version contains this commit? |
|
Check out Windows Terminal Canary. The next version with this should be out soon (there are currently some CI issues). |
|
OK, so thanks |
Closes #17264 Closes microsoft/edit#182 Long shot, but probably also... Closes #18579 Closes #19082 (cherry picked from commit 97f0a06) Service-Card-Id: PVTI_lADOAF3p4s4AmhmQzgWZBNU Service-Version: 1.22
|
ugh, i forgot to put this into 1.23. It's in 1.22 though! |
Closes #17264 Closes microsoft/edit#182 Long shot, but probably also... Closes #18579 Closes #19082 (cherry picked from commit 97f0a06) Service-Card-Id: PVTI_lADOAF3p4s4AxadtzgdOWF0 Service-Version: 1.23
Closes #17264
Closes microsoft/edit#182
Long shot, but probably also...
Closes #18579
Closes #19082