You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far, GitHub doesn't seem interested in supporting this. One possible solution would be to submit a PR to https://github.com/github/linguist to add support for Spack spec syntax highlighting. I'm not sure if they'll allow this, since Spack's specs aren't exactly a "programming language", but it's worth a shot.
It looks like they require a "language" to be popular on GitHub (at least 200 repos use it). Not sure if we can count repos with spack.yaml files since that's really just a YAML file, not a Spack spec syntax, but we have plenty of those: https://github.com/search?q=filename%3Aspack.yaml&type=Code
It would be awesome if we could add GitHub syntax highlighting support for Spack specs.
Rationale
Right now, if I share a Spack spec on GitHub, it looks like:
It would be much easier to read if it looked like:
Description
Ideally, users would be able to do something like:
Additional information
It looks like being able to specify a custom repo-specific language is a common feature request:
So far, GitHub doesn't seem interested in supporting this. One possible solution would be to submit a PR to https://github.com/github/linguist to add support for Spack spec syntax highlighting. I'm not sure if they'll allow this, since Spack's specs aren't exactly a "programming language", but it's worth a shot.
Here are the instructions for adding support for a new language: https://github.com/github/linguist/blob/master/CONTRIBUTING.md#adding-a-language
It looks like they require a "language" to be popular on GitHub (at least 200 repos use it). Not sure if we can count repos with
spack.yaml
files since that's really just a YAML file, not a Spack spec syntax, but we have plenty of those: https://github.com/search?q=filename%3Aspack.yaml&type=CodePinging some main contributors to linguist to see if they have any thoughts on this: @josh @arfon @pchaigno @tnm @Alhadis. If you instead want me to open an issue on https://github.com/github/linguist for discussion let me know.
The text was updated successfully, but these errors were encountered: