Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Refactor VT control sequence identification #7304
Refactor VT control sequence identification #7304
Changes from all commits
c60de41
6a97e81
31e83dd
97250a0
b06e2b4
fcfb41f
f96249c
a296252
8485002
c885d44
56c1635
8dd0c55
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Are we worried at all about using a
wchar_t
here as opposed to only validchar
values?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.
Yeah, there are actually some cases when this needs to be a full
wchar_t
in the input state machine - pressing something lik Alt+ € on a european keyboard will end up being encoded asESC €
so the final char in that case is going to be more than a byte. But there are no intermediates involved in that situation, so we just interpret the final id as awchar_t
when processing it. It's not as clean a solution as I'd like, but it's workable.