Fix Go's variables

[keithrussell42]

The Go syntax causes some schemes to colour all variables of any kind
with the "variable" colour. This can also be seen with the
built-in "Sixteen" colour scheme (and, indeed, with the original Base16
it came from). Without the change in this commit there is no instance
of a variable with foreground which contrasts with, say, Python where
most variables appear with the foreground colour. In the case of
Solarized light it's a "sea of blue".

An example in Python shows the expected behaviour.

if not os.path.exists(repo_name):
    return False
for fname in ["refs", "HEAD", "objects", "hooks"]:

"os", "path", "repo_name" and "fname" are all set to the default
foreground.

This Go code, however does not.

fileHeader := make([]byte, exifHeaderSize)
if _, err := data.Read(fileHeader); err != nil {

"fileHeader", "exifHeaderSize", "err" (both instances) and "data" all
display as the variable colour (blue, in the case of Solarized light
theme).

I'm not expecting the syntax file to change any time soon (changing the
way the syntax definition works could have drastic downstream effects).
Working around it in the scheme seems like the right approach. I
believe JavaScript has a similar variable workaround.

[braver]

I believe JavaScript has a similar variable workaround.

Yes, I don't think the syntax it at fault really, it's just that in Solarized all variables are blue. Except in most cases they are switched back to the foreground color. PHP is generally a sea of blue as well. There is no real reason for all of this, it's just the output several inconsistent systems coming together: there is no solid spec for Solarized so it itself is inconsistent (although I did try to improve it there), the syntaxes used to be wildly inconsistent too.

This looks like a good improvement though, I have nothing against it. Let's ship it!

And thanks for the donation by the way, it is very much appreciated ❤️