-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
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
VS2022 Colouring is broken when resetting "Fonts and Colors" to default values #13927
Comments
It does not reproduce in 17.3 |
Caused by new preview feature in VS: dotnet/roslyn#64168 Fix at the moment is disabling C#/VB LSP semantic tokens experience under Environment -> Preview Features. |
@vzarytovskii so this still repros with the above preview feature on. The matching roslyn issue is here. In the light of LSP 👀 , I'd say it would be enough if this VS setting just doesn't have an effect on F# (as opposed to trying to somehow propagate the logic thru the Roslyn interfaces) - do you agree? |
We talked with @dibarbet about this one:
On the other hand, I get disappearing colorization quite often, but only when working with our repo - and also it then randomly appears again, so my case might be unrelated. Based on this and low activity here for the 2 years, I'll deprio this to Medium for now. |
DISCLAIMER: Please, don't try reproducing it on your VS 17.4+ instance, since you will likely have a broken colouring till the fix is released.
When resetting fonts and colors to default values (Tools -> Options -> Environment -> Fonts and Colors), reloading VS and deleting
.vs
, VS treats everything as plain text (except keywords):The text was updated successfully, but these errors were encountered: