Post #2136639
2026-04-29 04:53 UTC
1/N: Okay, I'm going to need some help with this from some #Neovim and #LSP fans/experts.
The Typescript LSP server behaves differently between the CoC and Mason plugin frameworks. I have the colorscheme set up such that hovered symbols highlight in green for read refs, and red for write refs. This work in Coc, but not in Mason. Indeed, with verbose logging, the LSP seems to be returning different data for the symbol's "kind" -- a string under Coc, but an integer under Mason.
Replies (1)
-
@ewhac@mastodon.social 2026-04-29 05:50
2/2: Acto Microslop's LSP standards page, symbol "kind" is supposed to be an integer (0 == generic, 1 == read, 2 == write). So, I have no idea why I'm no longer seeing a distinction between reference kinds under Mason, nor can I explain why I'm seeing kinds as strings under CoC ("reference" and "writtenReference"). So far this only seem to affect Typescript (tsserver). Clangd and rust-analyzer appear to work as desired.