Syntax highlighting for Go code blocks only works when the block starts with "golang" not "go" or "Go", is there a way to change this?

[asherqnovick]

The syntax highlighting works fine, it's just that it only works for a Go code block if the block starts with "golang" which isn't really how anyone marks Go code blocks, the standard seems to be just "go." Is there something I can do on my end to make the syntax highlighting detect a block starting this way?

[keith-hall]

You're talking about Markdown code fences? You will want to edit this line:
https://github.com/sublimehq/Packages/blob/759d6eed9b4beed87e602a23303a121c3a6c2fb3/Markdown/Markdown.sublime-syntax#L1230
And then follow the instructions in bats readme to use your custom version

[asherqnovick]

Thank you, this appears to be what I need. Unfortunately I still can't get it to work and I'm not sure why.

The file you linked removes all markdown formatting after running 'bat cache --build'. I found this sublime-syntax file https://github.com/SublimeText-Markdown/MarkdownEditing/blob/master/syntaxes/Markdown.sublime-syntax#L1559 which appears to account for both go and golang. When using this, the default markdown formatting works, but still doesn't work with "go." Even after changing the line to ((?i:golang|go)) it won't register. Interestingly, if I change that line to just ((?i:go)) it still just does the default behavior, which indicates to me that it's not actually building this file for some reason. I know it's in the right directory because I can get an error message if I break the YAML in that file.

One more test I did was replacing all references of "golang" with "go" in the Markdown.sublime-syntax file and it still just does the default behavior. So basically no matter what I do in that file I either fully break the markdown formatting, or it just uses default behavior.

I'm really not sure what's going on here, any help would be appreciated.

[keith-hall]

Interesting, taking the Markdown sublime syntax file as of the commit I referenced and putting it in $HOME/.config/bat/syntaxes/, editing it to just scope # and * (as a test) worked for me. It may be worth giving it a distinct file name, plus name and file_extensions inside the yaml contents, and check it shows up in bat --list-languages as a debugging step, and manually enforcing that syntax with bat -l distinct_syntax_name_here path/to/markdown_file