For example, https://imgur.com/a/ia2GCgg -- top is VSCode, bottom is Zed. Both using Svelte, and using a similar theme.
- Angle brackets are a different color
- Capitalized built-in components are a different color
- Boolean props are a different color
- Brackets are colored differently than text.
The inspector is a game changer, clicking into these specific things in the preview they provide is super helpful.
I found one extension from a web search. Did you try this? https://zed.dev/extensions/svelte
But those are syntax highlights. What does this have to do with theming?
I'm not a Zed user, but https://zed.dev/docs/reference/all-settings#colorize-bracket... surely you can configure those.
The theme builder is good and easy to use, and I only needed a few minutes to make my own.
Syntax coloring is almost there, but still lacking (I use C/C++) Small visual adjustment like line height in the UI text is not configurable enough (only two settings)
Scrolling should have a smooth option, nothing prevents it, it should be super easy to add, I find it easier on the eyes when I move around code, especially on a 240Hz monitor.
The editing experience is good, quick launch, no crashes, responsive, not too memory hungry.
Besides, I never work on a laptop.
And this is a lame excuse. Smooth scrolling should also work when using keyboard with and pageup/pagedown, at least as an option and with some tuning preferences.
also wrt scrolling, mice like the logitech mx master actually have what is in my opinion a much better solution where the scrollwheel is not stepped and has scrolling inertia, allowing you to have the same level of precision with scrolling as you do with a touchpad (im not sure if the vertical wheel on it is the same but regardless). Its in my opinion a similar jump in capability for mice as continous triggers were for game controllers. Something that must have been initially quite notable, but slowly became expected behaviour (except on the switch for some reason but whatever i guess)
The defaults all feel very low contrast, gray on gray that makes the experience feel dull and off putting to me, even if the editor itself is great.
I usually look for a dark theme that looks good and then make a custom version with darker the background colors and brighter the foreground colors.
Maybe it's time for to start publishing high contrast dark themes instead of just fixing it for myself.
But I understand your point, no reason for it not to come with a couple good high contrast dark themes.
> The page you are trying to reach either does not exist, has been removed or you are not authorized to view it.
Whats next, ads inside file searches? (ubuntu blundered this way and soured the community) - "LQQKING for something? try new ai search by blah blah corp!"
So it's hard to 'invest' my time tweaking my editor and theme only to have it start to betray me in the future. VSCode has already gone down this path - signing commit messages with 'copilot'
In the end I fed some screenshots (and original ST4 config) to AI studio and it came up with something workable but not exactly a replica. Naturally different editors have different semantic tokens.
Last time I checked (about half an year ago) it was hardcoded and unconditional, so disabling it required a patch.
At the moment it seems it's great for personal development and development in environments where concerns around IP are less of an issue.
It's not so clear how to use it in corporation context where you'd be in breach of employment contract accidentally because defaults mean sending confidential IP to 3rd parties.
"markdown_preview_font_family": "Fira Sans Condensed",
"markdown_preview_theme": "Ayu Dark",
edit: clarity
It was added a few months ago if I remember correctly.