Nathan Ridge

> Looks like this is the last one that went in: [llvm/llvm-project@f782d9c](https://github.com/llvm/llvm-project/commit/f782d9c7002edaaf56c06a6cc1775f8f67713a29) For future reference, how did you determine this?

Thanks. To summarize: > I am currently using LLVM 11. Does that contain the new clangd with this feature? No, it does not. You'd have to use a weekly snapshot...

Going to copy over a comment from the duplicate issue #149 which is relevant: This does work in clangd 12 using the new standard `semanticTokens` protocol. Each preprocessor-disabled line gets...

It's worth noting that preprocessor-disabled regions are the _only_ thing for which clangd sends `comment` semantic tokens. (Actual comments are styled client-side and do not get semantic tokens.) So, you...

> Also even with the current way there's a bug: > > ```c++ > #ifdef PLATFORM_X > ... > #elif PLATFORM_Y > ``` > > It marks `#elif PLATFORM_Y` as...

> Ok that's unexpected. So everything that doesn't get a token is a comment? Otherwise it would have to know the comment styles for all languages. No; besides comments, other...

> I'm not sure yet if there is a way to extend the current implementation to achieve this more flexible styling, or if I should resurrect my patch. Opinions are...

> Does anyone know if there a way to simply disable the inactive region code from changing color at all? Clangd doesn't parse the inactive branches, so it's not going...

`"clangd.semanticHighlighting"` controls the old, clangd-specific semantic highlighting protocol that was used before LSP had a standard one, and has been removed in newer clangd versions. The current one is gated...

Dupe of #275. Also related to the discussion of "strong workspace mode" in https://github.com/clangd/clangd/discussions/907. I think the proposed behaviour would be useful and desirable in strong workspace mode (and that's...