Thank you very much for working on this. This works for me:

{
  programs.zed-editor = {
    enable = true;
    userSettings = {
      theme = {
        dark = lib.mkForce "Catppuccin Macchiato";
      };
    };
  };
}

Thank you very much for working on this. This works for me:

{
  programs.zed-editor = {
    enable = true;
    userSettings = {
      theme = {
        dark = lib.mkForce "Catppuccin Macchiato";
      };
    };
  };
}

Happy to see it working! I'm just working on a way to keep compatibility with 24.05... or just give up and wait for 24.11 to release 😆

Probably isn't my place to comment but does this implementation take the accent/flavour combinations from the GitHub release? We actually publish all the different accents on GitHub release but not via the editor iirc.

Probably isn't my place to comment but does this implementation take the accent/flavour combinations from the GitHub release? We actually publish all the different accents on GitHub release but not via the editor iirc.

Currently no. We use the extension from the official repos. We likely could support that use case however!

I actually need to understand again why we didn't publish them all via the editor, perhaps @tecandrew can explain that again (and subsequently document that reason somewhere if still valid)

iirc, it was discussed on the Discord. I just made the decision to not flood the list of themes on a user's Zed editor instance with each Flavor when they download the Catppuccin extension

I'd also like to use the GitHub release as mentioned above. Not sure how good of an idea that is in practice though (as I have still yet to use Zed), so totally up to you

I'd also like to use the GitHub release as mentioned above. Not sure how good of an idea that is in practice though (as I have still yet to use Zed), so totally up to you

I'm noticing now if we wanted that we would need the ability to fetch release artifacts, or to start work on in house derivations.