0

My color settings are for a black background of the editor and are "all white" for the text except for the curly brackets, for those I have separate colors.

Now, when I make a typo like missing a bracket or parenthesis, the editors is triggered and easily shows the error in red, that's the color settings for error, BUT if I mistype a variable or functions name what it does it puts a tiny underline under the first letter which is hard to see.

I have changed any possible setting in the json file for the color settings that I thought they could have anything to do with the color setting for such typos and nothing does the job. I asked the Google AI, which no matter how I worded the question and the request, it ended up with

"workbench.colorCustomizations": {
    "editorError.foreground": "#FFFF00", // Changes the color of the error squiggle
    "editorError.border": "#FFFF00" // Changes the color of the border around an error
}

Which only affects the color settings for errors but not when there is a typo and the editor can't fin a variable with such name.

So the editor knows something is wrong, it even gives me a suggestion how to fix it, but I have no way of changing how the editor displays the whole name so I can easily spot it, now obviously once I run the code, but I want to be able to see it in the editor while I'm writing the code or checking it later on.

Is there a way to set them the way I want?

3
  • This single-char underline is just by the spell checker, and not by semantic analysis, AFAIK. Isn't Javascript one of these languages incapable of detecting misspelled identifiers? Commented Oct 25 at 6:14
  • No, it's not a spell checker that does that, an identifiers doesn't have to be an actual words so a spell checker here is useless, and it's not the language itself that detects the misspelled identifiers it is the IDE in this case VSC, this happens while the code is still being edited, not during its execution. Properties can be declared on the go, so if those get misspelled good luck finding before the code is run, but identifiers are a different story and the VSC keeps track of them. Commented Oct 25 at 6:53
  • The root of the problem is that you haven't defined what mistyped is. Do you mean the case of typing undefined identifier? Also, how do you imagine the process of typing? When you start typing a word, you get intermediate values as you type, and, typically, they will be shown as mistyped. Do you really want it? Commented Oct 26 at 16:02

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.