Customising filetypes

[olimorris]

Hey @amaanq. Moving the discussion over here.

I have filetype highlights set out like this:

    highlights = {
      -- Ruby
      ["@function.ruby"] = { fg = "${blue}", style = "bold" },
      ["@function.call.ruby"] = { fg = "${blue}", style = "bold" },
      ["@include.ruby"] = { fg = "${blue}", style = "italic" },
      ["@parameter.ruby"] = { fg = "${fg}", style = "italic" },
      ["@symbol.ruby"] = { fg = "${cyan}" },

      -- Yaml
      ["@field.yaml"] = { fg = "${red}" },
      ["@string.yaml"] = { fg = "${green}" },
  }

Fancy trying for Rust?

[amaanq]

oh that's neat for specific languages, but Rust has a lot of unusual operators, for example the try_expression I mentioned earlier is a ? at the end of a result or option, how would that be customized in Rust?

https://github.com/tree-sitter/tree-sitter-rust here's the Rust grammar for tree sitter if you want to maybe take a look, I want to really separate the components like how vscode has done it, I really liked it

[olimorris]

With these

      ["@operator.rust"] = { fg= "${fg}" },
      ["@punctuation.bracket.rust"] = { fg= "${yellow}" },
      ["@constant.builtin.rust"] = { fg= "${cyan}" },

I can get to this:

EDIT: Sorry this didn't post earlier

[olimorris]

thanks! it was actually @constant.builtin.rust, but that fixed the Some, None, Ok, Err colors! do you happen to know how to color enum items?

enum Color {
    Red,
    Blue,
    Green,
}

normally, enum items are orange but I'd like them to be cyan (and thats the default in vscode)

I think we're hitting the limit of what is exposed via Treesitter:

Can't seem to find anything specifically related to enums

[amaanq]

Ahh I see, that's really unfortunate. Thank you for the help so far!

[olimorris]

@amaanq could you share your final Rust configuration please? I'd like to incorporate into the colorscheme

[amaanq]

Sorry for getting back so late, I hadn't noticed your message until I checked back here again! Here's my current Rust config!

I also added a toml config as by default properties are purple in vscode's onedarkpro theme, might be nice to add too

highlights = {
    ["@constant.builtin.rust"] = { fg = "${cyan}" },
    ["@field.rust"] = { fg = "${red}" },
    ["@function.builtin.rust"] = { fg = "${cyan}" },
    ["@function.macro.rust"] = { fg = "${orange}" },
    ["@keyword.rust"] = { fg = "${purple}" },
    ["@label.rust"] = { fg = "${white}" },
    ["@operator.rust"] = { fg = "${fg}" },
    ["@parameter.rust"] = { fg = "${red}", style = "italic" },

    ["@property.toml"] = { fg = "${purple}" },
}

I can also upload a golang config within a week or so, just a bit busy atm and I haven't touched go in a bit

While we're on the topic of highlights/theming, something that has been irking me is how a diagnostic warn/error will color the text with the type (red for err, yellow for warn, etc). I don't particularly like this and only want the undercurls. I noticed setting undercurl to true in the options does add the undercurls, but it does not turn off this text highlighting, here's an example:

Although it is somewhat of a false positive warning, the matter at hand is I just don't want capabilities (on the left) to be yellow in color, I want it simply to have a yellow undercurl. Let me know how to fix this, thanks!

[olimorris]

@mmirus and @mrjones2014 - Are you using the original filetype highlights at all? I'm looking to deprecate them soon in favour of the "new" treesitter filetype highlights.

[mrjones2014]

Nope, the only thing related to a specific filetype I have is these under the normal highlights config key:

        ['@keyword.operator.lua'] = { fg = '#d55fde', style = 'italic' },
        ['@operator.lua'] = { link = '@keyword.operator.lua' }

[mmirus]

Nope! Only the new syntax in highlights now. Thanks for asking.

[olimorris]

Super. I'll put a deprecation notice up and warn people and remove in a week or two. Thanks both.