Route "Device Status Report" responses correctly #72
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.
As reported in git-for-windows/git#3579, when using MSYS2 runtime v3.3.3 in a regular Git Bash, after
git config -e --global
launchedvim
and the editor was closed, seemingly random characters are "ghost-typed". Concretely, I saw1R77;30502;0c10;rgb:bfbf/bfbf/bfbf11;rgb:0000/0000/0000
being "ghost-typed" every time Git had called vi for editing a file.To be precise, the hexdump -C output is this:
This is the response for a
CSI [ 6n
request, and the response was clearly routed to the terminal by mistake instead of the process that requested it.The regression was actually introduced into v3.2.0, but not noticed earlier. I reported the issue after trying to figure out a workaround for three days, without success, and the original author of the commit introducing the regression provided a patch that works around it. I do not yet understand the patch, but let's take the patch for now because the regression is pretty severe.
While at it, also include a fixup that handles two previously unhandled instances of the
cygwin-pty
pipe (which is renamed tomsys-pty
in MSYS2) that I spotted while working on this bug.