-
Notifications
You must be signed in to change notification settings - Fork 7
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
The 'invalid' scope should be more obvious #68
Comments
I’d prefer yellow and black, but I strongly agree. |
@Monokai would you mind taking a stab at this? Here's a concrete example: Open a new document, set the syntax to Using the default color scheme, Using any Monokai Pro color scheme, this is what we see: The scope being used here is {
"name": "Invalid",
"scope": "invalid",
"foreground": "var(white2)",
"background": "var(red)"
},
{
"name": "Invalid deprecated",
"scope": "invalid.deprecated",
"foreground": "var(white2)",
"background": "var(orange2)"
} |
In the meantime, anyone could customize the theme themselves to get around this by taking the following steps. Open the Command Palette and select "UI: Customize Color Scheme". Under the {
"name": "Invalid",
"scope": "invalid",
"font_style": "normal",
"foreground": "var(white)",
"background": "var(red)"
},
{
"name": "Invalid deprecated",
"scope": "invalid.deprecated",
"foreground": "var(white)",
"background": "var(orange)"
} |
I've adjusted this in 1.1.21. I didn't adjust the background though, because I found that while you're typing, the partly typed code is often invalid, so you would have a lot of visual flickering. I agree though that more prominent colors for invalid code are easier to spot when you quickly scroll through your code. So I think a red foreground color with an underline is a good compromise here. |
Currently it seems
invalid
only makes the text italic and doesn't change colors at all.Most color schemes do something like: (red background, bright foreground) and I feel something closer to that would be useful.
The text was updated successfully, but these errors were encountered: