more catppuccin treesitter coloring #7
Conversation
tecandrew
commented
Mar 25, 2024
tecandrew
commented
- add more catppuccin colored treesitter syntax (from vim/neovim)
- more coloring definitions
- fix some minor visual bugs
template.hbr
Outdated
| "module": { | ||
| "color": "#{{lavender}}", | ||
| "font_style": "italic", | ||
| "font_weight": null | ||
| }, |
There was a problem hiding this comment.
We've moved away from lavender while defining the newer style guide, I'd be curious how VSCode highlights modules - I'd imagine its yellow?
There was a problem hiding this comment.
it is indeed yellow!
template.hbr
Outdated
| "string.regex": { | ||
| "color": "#{{pink}}", | ||
| "color": "#{{peach}}", | ||
| "font_style": null, | ||
| "font_weight": null | ||
| }, |
There was a problem hiding this comment.
This should stay pink as per updates in VSCode
There was a problem hiding this comment.
Regex should be pink but if it can be more in detail, it should inherit the other colour mappings (e.g. numbers in regex should be peach, lookaheads being blue since they act like a function taking values, etc) - See VSCode's PR on this (catppuccin/vscode#263)
| "string.special.symbol": { | ||
| "color": "#{{rosewater}}", | ||
| "font_style": "italic", | ||
| "font_weight": null | ||
| }, |
There was a problem hiding this comment.
We've moved away from rosewater in the newer style guide too, I'm curious how VSCode highlights these?
There was a problem hiding this comment.
We had some discussion about this on the discord, will update the style guide soon but this should now be peach
The reasoning being that these symbols are usually immutable/constants in languages
| "string.special.symbol": { | |
| "color": "#{{rosewater}}", | |
| "font_style": "italic", | |
| "font_weight": null | |
| }, | |
| "string.special.symbol": { | |
| "color": "#{{peach}}", | |
| "font_style": "italic", | |
| "font_weight": null | |
| }, |
| "variable.member": { | ||
| "color": "#{{lavender}}", | ||
| "font_style": null, | ||
| "font_weight": null | ||
| }, |
There was a problem hiding this comment.
Looks like treesitter describes this as:
@variable.member ; object and struct fields
and in VSCode / JetBrains, we kept this as text:
so this should kept as text
| "variable.member": { | |
| "color": "#{{lavender}}", | |
| "font_style": null, | |
| "font_weight": null | |
| }, | |
| "variable.member": { | |
| "color": "#{{text}}", | |
| "font_style": null, | |
| "font_weight": null | |
| }, |
| "variable.member": { | ||
| "color": "#{{lavender}}", | ||
| "font_style": null, | ||
| "font_weight": null | ||
| }, |
There was a problem hiding this comment.
Looks like treesitter describes this as:
@variable.member ; object and struct fields
and in VSCode / JetBrains, we kept this as text:
so this should kept as text
| "variable.member": { | |
| "color": "#{{lavender}}", | |
| "font_style": null, | |
| "font_weight": null | |
| }, | |
| "variable.member": { | |
| "color": "#{{text}}", | |
| "font_style": null, | |
| "font_weight": null | |
| }, |
| "string.special.symbol": { | ||
| "color": "#{{rosewater}}", | ||
| "font_style": "italic", | ||
| "font_weight": null | ||
| }, |
There was a problem hiding this comment.
We had some discussion about this on the discord, will update the style guide soon but this should now be peach
The reasoning being that these symbols are usually immutable/constants in languages
| "string.special.symbol": { | |
| "color": "#{{rosewater}}", | |
| "font_style": "italic", | |
| "font_weight": null | |
| }, | |
| "string.special.symbol": { | |
| "color": "#{{peach}}", | |
| "font_style": "italic", | |
| "font_weight": null | |
| }, |
|
will open another PR another time to update these, since this is a bit out of date already 🫡 |
