Support more syntax tokens for theme configuration

[zarifpour]

Check for existing issues

• [X] Completed

Describe the feature

Proposed Solution:

1. Expand Theme Configuration: Extend the theme's configuration file to include more syntax tokens, enabling granular customization for different code elements.

2. Language-specific Support: Allow themes to define colors for syntax tokens specific to different programming languages.

This approach will enhance user experience by allowing more detailed and language-specific theme customization.

If applicable, add mockups / screenshots to help present your vision of the feature

No response

[maxdeviant]

@zarifpour Do you have specific examples of things that we don't currently support?

[zarifpour]

I can look for a better example, but here's a quick one. Let me know if it makes sense:

I don't think it's possible to color these specific elements, where in VSCode I can target these specifically and configure their colors and font style.

[drcongo]

I've been porting my personal Sublime Text theme to Zed and found a few things that I couldn't seem to set colours for...

Sublime

Zed

A quick list of Python tokens (though bear in mind that I may have just failed to find the right keys)...

• imported modules and functions get the same colour as classes / functions within the file
• Couldn't find a token to colour the dunders __all__ or __init__ (note that they're different used inside or outside a class too
• The “%(name)s” inside a string
• Function / method args
• self which is a big one for readability
• Exceptions like the TypeError in the screenshot
• Lots of things in the f-string

I think there's probably a few more too, these were just the ones visible in the screenshots of a random page from the Django codebase. Apologies if all these are actually possible and I'm just adding noise to the thread.

[pimmee]

Here's an example issue I created in the VSCode Dark Plus theme extension repo, which looks completely different in Zed vs VSCode.

When I tried to fix the colors and make a PR, I also quickly ran into issues with too few specific syntax tokens, especially for Typescript. Some examples include return or await. When I looked into how VSCode does it I recall seeing they have language specific scopes.

Would love if the color theming can be improved!

[codeitlikemiley]

I guess this is the same as my issue https://github.com/zed-industries/zed/issues/13961

I really need to make rust syntax highlighting more noticeable... its hard to work with all types having same color

[everdrone]

Also Rust attributes have inconsistent highlighting zed:

vscode:

---

And Rust doc comments don't have any special highlighting. In vscode, rust doc comments get some flavor of markdown highlighting (links to crate items, types, functions, constants, with their respective color in the active theme), plus code blocks get rust syntax highlighting vscode:

[ehamiter]

This might also help cover my issue-- I'm unfamiliar with what order new LSPs/treesitters/syntax tokens occur to support colorization. Here's an example of a django template / html file that is in Sublime Text that is being highlighted:

...and here is an example of the same django template in Zed that is not being highlighted:

---

https://github.com/zed-industries/extensions/issues/1303