3 ms·
Misleading headline. > the actual bug: let's add to our code.. an emoji! Any emoji. > rust-analyzer adheres to the LSP spec. And lsp-mode doesn't. So “emojis
by aendruk 4y ago
Misleading headline.
> the actual bug: let's add to our code.. an emoji! Any emoji.
> rust-analyzer adheres to the LSP spec. And lsp-mode doesn't.
So “emojis break an Emacs extension”.
Though for me the real takeaway is that LSP specifies UTF-16 offsets. That sounds unpleasant to work with.
- deleted 4y ago[deleted]
- Ygg2 4y agoThanks, for people looking for bug, see https://github.com/emacs-lsp/lsp-mode/issues/2080 https://github.com/emacs-lsp/lsp-mode/issues/2080
- pja 4y ago> Though for me the real takeaway is that LSP specifies UTF-16 offsets. That sounds unpleasant to work with. Speaking as someone who has written an lsp server: yes, it is indeed unpleasant to work with.
- stouset 4y ago> Though for me the real takeaway is that LSP specifies UTF-16 offsets. That sounds unpleasant to work with. It is beyond time for UTF-16 to die. And yet it looks like we're stuck with it for the inevitable foreseeable future.
- puffoflogic 4y agoWe'll be stuck with UTF-16 as long as we have Unicode, it would seem. The character set itself has to have a hole in the middle of it for the sole purpose of working around UTF-16 limitations.
- deleted 4y ago[deleted]