summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
Diffstat (limited to 'tools')
-rw-r--r--tools/gen_themes.zig14
1 files changed, 9 insertions, 5 deletions
diff --git a/tools/gen_themes.zig b/tools/gen_themes.zig
index be5fde2f..30808dfe 100644
--- a/tools/gen_themes.zig
+++ b/tools/gen_themes.zig
@@ -11,9 +11,10 @@
//!
//! Why vendored and not read out of ~/05-genizah: `zig build` must work on a
//! fresh clone with no network and no helix checkout. It is the WHOLE of what
-//! both projects ship — helix's 214 runtime themes and zed's three families,
-//! 1.5MB of text — because "which ones are worth having" is not a question a
-//! build tool gets to answer on the user's behalf.
+//! both projects ship — helix's runtime themes and zed's three families —
+//! because "which ones are worth having" is not a question a build tool gets
+//! to answer on the user's behalf. The one exception is helix's copy of a
+//! theme pardes ports by hand (src/themes/: dracula, nord, ...): not vendored.
//!
//! NAMES. A helix theme is its file stem; a zed variant is its `name` slugged
//! with `_zed` on the end. Both projects ship gruvbox, ayu and one, so the
@@ -21,7 +22,10 @@
//! variant is one rule instead of eight exceptions — it also keeps a name from
//! moving when the other source gains or loses a file. helix's own `acme.toml`
//! is vendored as `acme_helix.toml` for the same reason, since pardes ships an
-//! acme of its own; the file is otherwise untouched. Two themes answering to
+//! acme of its own; the file is otherwise untouched. So are `monokai`,
+//! `ayu_dark` and `nord` as `<name>_helix.toml`, kept (unlike helix's other
+//! copies of themes ported here) because helix themes inherit them; those
+//! `inherits` lines name the renamed file. Two themes answering to
//! one name is a bug (`Theme <name>` would silently pick one), so src/colors.zig
//! asserts the ring's names are distinct at comptime.
//!
@@ -29,7 +33,7 @@
//! helix-editor/helix runtime/themes, each file keeping its author's header);
//! *.json are zed's (zed-industries/zed assets/themes). The licences sit beside
//! them as `<name>.LICENSE` — `helix.LICENSE` covering the runtime set, one per
-//! zed family, plus the twenty-two helix keeps in `runtime/themes/licenses/`
+//! zed family, plus the twenty-one helix keeps in `runtime/themes/licenses/`
//! for the themes it took from somewhere else (their names group by SOURCE, not
//! by file: `everforest.LICENSE` covers both everforest themes). build.zig's
//! directory read skips anything that is not a .toml or a .json, which is what