Bugs and suggestions for language-configuration.json

[RedCMD]

This report is just a list of different bugs, weirdness, suggestions, feature requests, notes and missing info; from within and around the language-configuration.json file
I can open a new report for any one of these items if needed

• Bug: "colorizedBracketPairs" only supports lowercase, but matching is case insensitive #197970

• Bug: Cant type > after { if {} and <> are defined as 'brackets' #149460

• Request: Split bracket indentating and bracket pair highlighting #141044

• Suggestion: colored angle brackets in rust #149719

• Bug: Match highlighting for <> does not work if they are *only* defined as "brackets" #150687

• Noteable: In release 1.67 multiple-character bracket match highlighting no longer works if any one character has a different foreground token or font style than any other character.
  TextMate grammar has given the $ italics, but not the { (The closing bracket does not care about the opening bracket's token)
  1.66: 1.67:

• Feature request: Allow match highlighting with the same opening and closing character
  If " is defined as both the opening and closing "brackets", vscode will mark all " as invalid
  1.66: 1.67:

• Noteable: Match highlighting does not work correctly with letters:
  

• Bug: Suggestions are not available if a word starts with a number even if "wordPattern" allows it
  
  

• Weird: Word highlighting won't highlight the word under the cusor if the ending character is a letter and the following character is also a letter
  But weirdly; it will still highlight other occurrences of the word in the document
  

• Bug: When embedding a language inside another; "comments", "colorizedBracketPairs" and "wordPattern" correctly uses the embedded languages settings. But "autoClosingPairs", "autoCloseBefore", "folding" and "indentationRules" do not work, and instead continue to use the parent's language settings
  Embedded languages do not use their own indentationRules settings #176034

• Feature request: Add a 'case-insensitivity' option to "wordPattern". Currently trying with (?i) will cause it to fail silently
  [folding] Support flags on folding.markers RegExps #72989

• Feature request: Allow a way to disable 'bracket colouring' for specific brackets, but still allow 'bracket pair highlighting'
  Either via a special token or just specifying the brackets
  For when you want to see bracket pairs without them changing colour. Would be useful for non-nesting bracket types
  e.g. comments, strings, ranged quantifiers (in regex) {2,3} and even for word based 'brackets' like If and EndIf
  Support coloring a subset of the matched brackets #170497

• Bug: Horizontal bracket guides do not work on wrapped lines if editor.wrappingIndent is set to none (or same and if there is no indentation)
  none: indent:
  Horizontal bracket guides break on wrapped lines in first column, if editor.wrappingIndent == "same" #149074

• Bug: https://code.visualstudio.com/api/language-extensions/language-configuration-guide does not list the new "colorizedBracketPairs" option. Nor does it say that "brackets" will implicitly enable all other options if not explicitly 'not defined' (TODO: needs more info)

[alexdima]

Sorry for my slow reaction time on this issue.

[hediet]

Thanks for this detailed list!

Please open a new issue for each item and list them here (like you did with the first four bullet points). That makes discussing them individually easier!

I'm very sure some of your points are duplicates of existing issues though.