HolyC Syntax Highlighting?

[ghost]

Feature Description

Would it be possible to get HolyC syntax highlighting for Gitea? I am working on a Git site dedicated around the language, but the fact that there is no syntax highlighting really takes away from the general aesthetic.

HolyC is really similar to C in terms of syntax except for really variables and function names. Below is a screenshot of said implementation on GitHub.

I understand this may be a very niche topic, and likely may not be added, however in that case, could I atleast be provided with documentation on writing the syntax highlighting manually? Thanks.

Screenshots

[JakobDev]

You might want to create a Issue for Chroma, which is the Syntax Highlighter used by Gitea. If you want it to do yourself, you can find the Lexer for C here. If you have good knowledge of the Syntax, you can create a Lexer for HolyC based on this and make a PR.

[wxiaoguang]

Workaround: or use gitattributes to tell the highlighter that some files are C code. Like this one:

• PHP Syntax Highlighting does not working in review mode #21970 (comment)

[ghost]

You might want to create a Issue for Chroma, which is the Syntax Highlighter used by Gitea. If you want it to do yourself, you can find the Lexer for C here. If you have good knowledge of the Syntax, you can create a Lexer for HolyC based on this and make a PR.

Ah my nightmare, Regex. I knew I'd have to learn it eventually. Honestly though, thank you so much for this, I don't think HolyC will be that hard to manufacture using this. Appreciate it.

[silverwind]

If it works with c syntax, you could contribute the addition of the file extension (assuming it has a unique one) to chroma's c lexer and gitea will then automatically pick it up based on the file extension after we update chroma.

[silverwind]

As per github-linguist/linguist#4512, Github does match it based on the .hc extension, so unless this extension is already in use at Chroma somewhere else, it should be possible to get it added.

[ghost]

Realistically, this looks like it should be a breeze to do considering it seems that the GitHub format is very similar to Chroma. From what @silverwind linked, I found this: https://github.com/codingdandy/holyc.tmbundle which should be sufficient.

[silverwind]

Yeah, so the job is to start with https://github.com/alecthomas/chroma/blob/master/lexers/embedded/c.xml and adapt the individual rules based on https://github.com/codingdandy/holyc.tmbundle/blob/master/Syntaxes/HolyC.tmLanguage to create the chroma lexer.

My earlier idea of just adding an alias to the C lexer is not right, the language is too different from C to be considered an alias.

[ghost]

I've gone ahead and made a pull request for this on Chroma: alecthomas/chroma#750

[silverwind]

Thanks, so we just need to wait until next chroma release and then update it.

[ghost]

Is that it @silverwind? I thought I had to edit "go-enry" or something

[silverwind]

For the syntax highlighting, chroma is enough.

https://github.com/go-enry/go-enry is used for the language stats bar, but it may be that they already support HolyC given that they source some data from linguist, but if you like, please double-check.

[ghost]

For the syntax highlighting, chroma is enough.

https://github.com/go-enry/go-enry is used for the language stats bar, but it may be that they already support HolyC given that they source some data from linguist, but if you like, please double-check.
Alrighty, looks like HolyC is already there. Is there any way to force my gitea build to use the latest of Chroma, not the latest version since my PR wasn't packaged but instead the branch?

Well I'm not sure if that worked, I figured I could do:

go get -u github.com/alecthomas/chroma
go mod tidy
TAGS="bindata sqlite sqlite_unlock_notify" make build

However on a repo it's still recoginzed as "PlainText":

I'm not sure if I was unable to get the latest commit, or if my additions dont work.

[silverwind]

Try:

go get -u github.com/alecthomas/chroma/v2@3ac94eea73f5de1bf6c864b9a7f4089514415090

[ghost]

That worked! Thanks all!