Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
False Positive: Source file is not valid UTF-8 #57
I can confirm that this still happens. How to reproduce:
My guess is it might be a bug in vscode client.
Seems like this is caused by the fact that all the offsets and lengths in Language Server Protocol is given as the amount of
Sounds difficult to fix without introducing UTF-16 aware
Edit: Nope, it's not UTF-8, it's UTF-16 as per specification. But
And what's worse, lsp-mode have no idea about these UTF-16 things, so positions coming from Emacs would be in UTF-8 characters.
Maybe we could use an UTF-8 iterator of std::string for working on