* monokai-color-theme.json: treat Python comment string blocks
...as comments too
* Update *all* themes to consider Python block string comments as comments
modified: extensions/theme-abyss/themes/abyss-color-theme.json
modified: extensions/theme-defaults/themes/dark_vs.json
modified: extensions/theme-defaults/themes/hc_black.json
modified: extensions/theme-defaults/themes/hc_light.json
modified: extensions/theme-defaults/themes/light_vs.json
modified: extensions/theme-kimbie-dark/themes/kimbie-dark-color-theme.json
modified: extensions/theme-monokai-dimmed/themes/dimmed-monokai-color-theme.json
modified: extensions/theme-monokai/themes/monokai-color-theme.json
modified: extensions/theme-quietlight/themes/quietlight-color-theme.json
modified: extensions/theme-red/themes/Red-color-theme.json
modified: extensions/theme-solarized-dark/themes/solarized-dark-color-theme.json
modified: extensions/theme-solarized-light/themes/solarized-light-color-theme.json
modified: extensions/theme-tomorrow-night-blue/themes/tomorrow-night-blue-color-theme.json
* Update all changes to use "string.quoted.docstring"
...instead of "string.quoted.docstring.multi.python", per
@aeschli's request here:
https://github.com/microsoft/vscode/pull/182162#issuecomment-1545296640
This way the comment formatting applies to *all* language quoted
docstrings, instead of just to Python.
* bring back python colorize tests
---------
Co-authored-by: Martin Aeschlimann <martinae@microsoft.com>
* Unfreeze Git Commit Message grammar II
Before this change, the upstream for the VSCode Git grammar was dead.
Also, the test setup for that project has been EOL since 2014, so even
just running the tests was difficult.
The replacement grammar, unlike the current grammar:
* Has a vscode-tmgrammar-test test suite that is runnable and passing
and that will run in CI for any PRs (in the upstream project)
* Has diff highlighting for Swedish as well as English (#133888)
* Highlights touched files both in Swedish and in English
Fixes#133888Fixes#168847
Ref: <https://github.com/walles/git-commit-message-plus>
And for the record, I was the one setting up the new Git Commit Message
project. And it was fun!
* Remedy review feedback
Retain the line-too-long subject line highlighting. Improved to
highlight only the too-long part, but same idea still.
Special case English language file operations keywords and retain the
previous classification of those. But fallback to op-and-filename
classification when that fails (like it will for Swedish git for
example).
* Update colorize test result
* Update script and cgmanifest
---------
Co-authored-by: Alex Ross <alros@microsoft.com>
* Add experimental default dark/light themes
* Update themes and name
* Add colorizer test results
* Update accent color
* Fix status bar no folder background issue
* Fix tree indent strokes
* Update lighter layer
* Fix breadcrumbs
* Update accent
* Update light lights and dark links
* Update colorizer test
Add Makefile tests for upgraded grammar: comma, comment, shebang.
1. Add comma separator for function calls and conditions.
2. Escaping a comment with an odd count of backslashes (\#, \\\#).
3. Match debian/rules files based on shebang.
Co-authored-by: Alex Ross <alros@microsoft.com>
Identifying specific symbols is a better fit for semantic highlighting instead of textmate as semantic highlighting prevents false positives
This keeps around a few of the most built-ins for now but we may revisit these in the future
* Add light HC theme and split quick pick options to light and dark
* Update colorizer tests
* Fix default HC name and add Beta tag to light HC theme
* Revert prettier updates
