VS Code Extension: Don't turn off highlighting of "invisible characters"

[DavisVaughan]

Bug description

In the VS Code Extension, for some unknown reason the extension ships with

      "[quarto]": {
        "editor.unicodeHighlight.ambiguousCharacters": false,
        "editor.unicodeHighlight.invisibleCharacters": false
      },

quarto/apps/vscode/package.json

Line 958 in faef822

"editor.unicodeHighlight.invisibleCharacters": false

I git blamed my way back but they seem to be tied to the "great migration" commit which is not useful for gaining context about why this is set
0afac7b

I believe that "editor.unicodeHighlight.invisibleCharacters": false is particularly harmful, as it prevents non-breaking spaces from being highlighted. I'd argue that if non-breaking spaces were highlighted, then this user would have been able to figure out their problem much faster:
posit-dev/air#381

Here are the docs for these two settings, I vote we remove the contributed configuration for both of these entirely:

This also aligns with my general principle that extensions should ship as minimal amount of contributed configuration as possible, because it will often just confuse users otherwise.

Steps to reproduce

No response

Actual behavior

No response

Expected behavior

No response

Your environment

No response

[DavisVaughan]

Oooh @lionel- has informed me that VS Code itself does this for plain text and markdown, so presumably it has something to do with these characters in the prose itself, and not in the code blocks?

[DavisVaughan]

Okay I've tracked down where VS Code itself started doing "editor.unicodeHighlight.invisibleCharacters": false for plain text and markdown:

microsoft/vscode#139201
microsoft/vscode@ce5d351

So it seems like the ⚠️ warning emoji uses "variation selectors" inside it, which are invisible? And they didn't want to highlight that in prose, so they turned it off for plain text and markdown.

But I wonder if something has changed in their implementation to be smarter about emojis since then, because if I turn "editor.unicodeHighlight.invisibleCharacters": true back on, then I get non-breaking space highlighting but I don't get a warning about the emoji, which seems good, so I'm not totally convinced we should follow VS Code's lead with this.