We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
The DAP uses utf-16 code units for offsets (ref: microsoft/debug-adapter-protocol#91).
Vimspector uses probably a mix of byte offsets and unicode codepoints.
To Reproduce
Add a line with a multi-byte character and a language (like TCL) that provides the column offset.
Expected behavior
Offsets are interpreted correctly according to the appropriate notion of "characters"
Actual behaviour
Not sure yet, i haven't tried it, but i expect tracebacks
The text was updated successfully, but these errors were encountered:
This has been clarified in microsoft/debug-adapter-protocol#285; the result is the same, it's UTF16 code units. Shrug.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
The DAP uses utf-16 code units for offsets (ref: microsoft/debug-adapter-protocol#91).
Vimspector uses probably a mix of byte offsets and unicode codepoints.
To Reproduce
Add a line with a multi-byte character and a language (like TCL) that provides the column offset.
Expected behavior
Offsets are interpreted correctly according to the appropriate notion of "characters"
Actual behaviour
Not sure yet, i haven't tried it, but i expect tracebacks
The text was updated successfully, but these errors were encountered: