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
Forgive me if I missed it, but I couldn't see a specification for the values of column offsets.
Examples:
text
column
I realise with LSP there is a bit of a fiasco with it being specified as UTF16 code units, is that also the assumption here?
The text was updated successfully, but these errors were encountered:
Today columns offsets are based on a UTF-16 string representation. But we are planning to make this negotiable via DAP capabilities.
Sorry, something went wrong.
So they are like LSP; UTF-8 code units?
No, LSP is based on a UTF-16 string representation which means that it uses 16-bit code units. And DAP uses the same.
Sorry yes I typod I mean utf 16 code units.
Thanks for the clarification.
weinand
No branches or pull requests
Forgive me if I missed it, but I couldn't see a specification for the values of column offsets.
Examples:
text
item is utf-8 encoded, what does thecolumn
items count ? bytes? or codepoints ? ).I realise with LSP there is a bit of a fiasco with it being specified as UTF16 code units, is that also the assumption here?
The text was updated successfully, but these errors were encountered: