Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-project themes (multiple active themes) #13300

Open
1 task done
norman784 opened this issue Jun 20, 2024 · 6 comments
Open
1 task done

Per-project themes (multiple active themes) #13300

norman784 opened this issue Jun 20, 2024 · 6 comments
Labels
enhancement [core label] setting Feedback for preferences, configuration, etc theme Feedback for theme configuration, accessibility, visual issues, etc

Comments

@norman784
Copy link

Check for existing issues

  • Completed

Describe the feature

I would love to customise the theme per project, the local settings does not support this override at the moment.

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

No response

@norman784 norman784 added admin read Pending admin review enhancement [core label] triage Maintainer needs to classify the issue labels Jun 20, 2024
@notpeter notpeter added theme Feedback for theme configuration, accessibility, visual issues, etc setting Feedback for preferences, configuration, etc and removed triage Maintainer needs to classify the issue admin read Pending admin review labels Jun 20, 2024
@notpeter
Copy link
Member

Interesting. I don't see this being an immediate priority, but it'd definitely be nifty to be able to visually differentiate between multiple open projects based on theme / color of the window.

I don't think it would make sense to specify theme overrides in a project specific .zed/settings.json because then any collaborators on that project would then be forced to use the same theme overriding their personal theme selections.

So this would be in a user's ~/.config/zed/settings.json with something like:

    "theme_override": {
        "proj1": "Solarized Dark",
        "proj2": "Solarized Light"
    }

Or were you thinking it'd be explicit override for a portion of a given theme?

    "theme_style_override": {
        "proj1": {
            "element.background": "#0b342d"
        }
    }

@notpeter notpeter added the needs info / awaiting response Issue that needs more information from the user label Jun 20, 2024
@norman784
Copy link
Author

I don't think it would make sense to specify theme overrides in a project specific .zed/settings.json because then any collaborators on that project would then be forced to use the same theme overriding their personal theme selections.

I didn't consider that scenario, but also I usually do not commit my editor preferences to the repository, because not everyone in a team uses the same editor.

@notpeter notpeter removed the needs info / awaiting response Issue that needs more information from the user label Jun 20, 2024
@notpeter notpeter changed the title Theme override Per-project themes (multiple active themes) Jun 22, 2024
@notpeter
Copy link
Member

Note I altered the title from theme override to reduce confusion.

There is an existing, similar but unrelated, experimental setting named theme_overrides:

  "experimental.theme_overrides": {
    "editor.background": "#000000"
  },

Doesn't help you (only works in global .zed/settings.json) but somewhat related.

@markiol
Copy link

markiol commented Aug 13, 2024

Would love to see that feature as well!
Apparently, the last one to switch from vscode!
I use two separate vscode projects for an api and a frontend, so It's really easy to distinguish between open projects based on the editor theme

@EliantenHolder
Copy link

This is a core part of my dev process too, I normally use a VSCode plugin called Peacock to differentiate editor windows currently (especially useful when working with multiple versions of the same codebase). So anyway to set different themes for different project/folders would be appreciated. I tried setting a theme in a project specific settings.json but it did not give the desired effect.

@tino
Copy link

tino commented Oct 23, 2024

Second that on the Peacock extension. If I could just give the top bar a different colour (via local .zed/setting.json is fine for me) that would make it much easier to recognise which of the 3-4 open Zed windows I need!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement [core label] setting Feedback for preferences, configuration, etc theme Feedback for theme configuration, accessibility, visual issues, etc
Projects
No open projects
Status: No status
Development

No branches or pull requests

5 participants