sublimehq
[Sublime] Add Syntax Test Results syntax
This PR proposes to add a Sublime package with Sublime Syntax Test Results syntax definition for highlighting syntax test result outputs with regards to https://github.com/sublimehq/sublime_text/issues/3022.
Thoughts:
- A package named "Sublime" does not yet exist on package control.
- The package name is generic enough to potentially take more Sublime Text related syntax files.
Maybe more suitable alternative package names are appriciated.
Syntax definition is designed to highlight ST's default syntax test result output - despite the proposal in https://github.com/sublimehq/sublime_text/issues/3022, which addresses a reformatted output.
I am definitely in favor of also reformatting the line display like in https://github.com/sublimehq/sublime_text/issues/3022#issuecomment-1937034498 because it is much easier to compare the expected selector and actual scope that way.
- The package name is generic enough to potentially take more Sublime Text related syntax files.
Are you thinking of moving the file patterns? That makes sense to me if this folder is added.
I didn't have certain syntaxes in mind - just found adding a package named Sublime Syntax Test Results with only one file/syntax inside rather too specific.
Not sure, what a good name for such ST related syntaxes would be.
Depending on how packages are finally built by sublimehq, I could also imagine creating a "Default" package in this repo. It however would require containing files to be added to "Default.sublime-package". Not sure if that's desirable.
I would also guess that the Default package makes sense as a holder of various built-in functionality and as something that cannot/should not be disabled because it is referenced in other built-in parts. Iirc there used to be problems for people that disabled the package with the regular expression syntax for some reason, for example.
However, it raises the question of whether it can/should be included inside of this repo in that case.
Closing as obsolete with regards to progress made in https://github.com/sublimehq/sublime_text/issues/3022.