diff options
| author | Gabriel Schneider <[email protected]> | 2026-07-31 09:59:08 -0300 |
|---|---|---|
| committer | Gabriel Schneider <[email protected]> | 2026-08-01 15:02:08 -0300 |
| commit | 5cf16eab0a4beec196e51bdcee731b899a2af07c (patch) | |
| tree | fc2e7afaab7796b3f32773e29d26b5969727475c /vendor/themes/wolf-alabaster-light.toml | |
| parent | 560ae0a63f7b5d354bad3ba13dd8ab26b5f0a870 (diff) | |
| download | pardes-5cf16eab0a4beec196e51bdcee731b899a2af07c.tar.gz pardes-5cf16eab0a4beec196e51bdcee731b899a2af07c.zip | |
every helix and zed theme on the machine, not a curated nine
228 in the ring: 3 pardes ships plus all 214 helix runtime themes and all 11
zed variants across its three families. No exclusions.
inherits is what this cost. 76 themes need it, so the reader is two passes now,
and the merge is WHOLE-KEY rather than field-wise because helix merges the
theme body at depth 1 — the three *_transparent themes clear their parent's
background with an empty table, and a field-wise merge would leave it painted.
I had that wrong until I read helix-view/src/theme.rs.
At 214 files the generator meets themes that are SPARSE rather than broken, and
the old fatal-on-anything-missing would have rejected them. Every fallback is
helix's own rule: no background at all means wear the terminal's, so bg and fg
go null (13 themes, correctly); the twelve RGB fields that cannot be null fall
back to ghostty's default palette entries 7 and 0, which is exactly what a
pardes terminal already paints an unstyled ANSI index as. fatal is kept for
what genuinely cannot be read.
Three real bugs surfaced only at scale: #ccc shorthand doubles the nibble
(helix's rule, 58 colours), a quoted inline-table key silently dropped a
selection colour, and four themes name a cursor background EQUAL to the page
because they are about to reverse that cell — taking it painted an invisible
move box. 0 degenerate themes out of 225 now: no fg==bg, no syntax colour on
its own background, no invisible box.
Collisions get an unconditional rule rather than a clever one: a zed variant is
always <name>_zed, because both projects ship gruvbox, ayu and one, and a
conditional tag would move a name when the other source changes. A comptime
assert holds it.
Cost: no-op build 0.257 -> 0.276s, a pardes.zig change 46.8 -> 47.5s, binary
+0.98%. The generator does 217 sources in 54ms.
NextColor stays and is no longer a way to REACH a theme — but the browse got
better, not worse: the generated half sorts by name, so its neighbours are that
theme's own family. theme.golden's fourth click moved from ayu_dark to acid,
which sorting 225 names does; themesel gained a tail capture proving row 228
renders.
Diffstat (limited to 'vendor/themes/wolf-alabaster-light.toml')
| -rw-r--r-- | vendor/themes/wolf-alabaster-light.toml | 169 |
1 files changed, 169 insertions, 0 deletions
diff --git a/vendor/themes/wolf-alabaster-light.toml b/vendor/themes/wolf-alabaster-light.toml new file mode 100644 index 00000000..6e1f041f --- /dev/null +++ b/vendor/themes/wolf-alabaster-light.toml @@ -0,0 +1,169 @@ +# wolf-alabaster-light.toml +# +# Author: Wolf <[email protected]> +# Project: https://github.com/wolf/alabaster-for-helix +# Download: https://raw.githubusercontent.com/wolf/alabaster-for-helix/main/helix/dot-config/helix/themes/wolf-alabaster-light.toml +# +# This is a light-background theme especically for the Helix editor. +# +# The most important part here is the syntax stuff, but the theme includes UI stuff specifically for Helix, as well. +# +# What I care about is: +# * Readable syntax, no matter the language +# * The error messages provided by the LSP +# * Anything special needed to make the UI non-surprising +# * Building a minimal definition +# +# I started from a couple important sources: +# * The [priorities and ideas](https://tonsky.me/blog/syntax-highlighting/) behind the Alabaster Theme (which exists for many editors) by Nikita Prokopov +# * His [actual repo implementing the theme](https://github.com/tonsky/sublime-scheme-alabaster) +# * A [theme template](https://github.com/joegm/helix-theme-template) on GitHub provided by joegm + +# I don't consider this to be done! I absolutely want feedback. I absolutely will continue to tinker. + +# GENERAL - Diagnostics (LSP errors/warnings) +warning = { fg = "highlight" } +error = { fg = "error-red", modifiers = ["bold"] } +info = { fg = "definition" } +hint = { fg = "punctuation" } +diagnostic = { underline = { style = "curl" } } + +# UI - Interface elements +"ui.background" = { bg = "bg" } +"ui.text" = { fg = "fg" } +"ui.text.focus" = { fg = "active", modifiers = ["bold"] } + +"ui.cursor" = { bg = "active", fg = "bg" } +"ui.cursor.primary" = { bg = "active", fg = "bg" } +"ui.cursor.match" = { bg = "highlight" } +"ui.cursorline" = { bg = "cursorline" } +"ui.cursorcolumn" = { bg = "cursorline" } + +"ui.gutter" = { bg = "bg" } + +"ui.selection" = { bg = "selection" } +"ui.selection.primary" = { bg = "selection-primary" } + +"ui.linenr" = { fg = "punctuation" } +"ui.linenr.selected" = { fg = "active", modifiers = ["bold"] } + +"ui.statusline" = { fg = "fg", bg = "panel" } +"ui.statusline.inactive" = { fg = "punctuation", bg = "panel" } + +# Bufferline - make active buffer clearly visible (like onelight-fixed-bufferline) +"ui.bufferline.active" = { fg = "fg", bg = "bg", modifiers = ["bold"] } +"ui.bufferline.background" = { bg = "bg" } +"ui.bufferline" = { fg = "punctuation", bg = "panel" } + +"ui.menu" = { fg = "fg", bg = "panel" } +"ui.menu.selected" = { fg = "bg", bg = "active" } + +"ui.popup" = { fg = "fg", bg = "panel" } +"ui.popup.info" = { fg = "fg", bg = "panel" } +"ui.window" = { fg = "punctuation" } +"ui.help" = { fg = "fg", bg = "bg" } + +# Jump labels - extremely visible +"ui.virtual.jump-label" = { fg = "jump-label", modifiers = ["bold"] } + +# Virtual text (inlay hints, etc.) - dimmed type color +"ui.virtual" = { fg = "inlay-hint" } +"ui.virtual.inlay-hint" = { fg = "inlay-hint" } +"ui.virtual.ruler" = { bg = "cursorline" } + +# LSP diagnostic inline/expanded text +"diagnostic.error" = { underline = { color = "error-red", style = "curl" } } +"diagnostic.warning" = { underline = { color = "highlight", style = "curl" } } +"diagnostic.info" = { underline = { color = "definition", style = "curl" } } +"diagnostic.hint" = { underline = { color = "punctuation", style = "curl" } } +"diagnostic.deprecated" = { fg = "punctuation", modifiers = ["crossed_out"] } + +# SYNTAX HIGHLIGHTING - Following Alabaster's minimal approach +# Only 4 categories get color: strings, constants, comments, definitions +# Everything else (keywords, variables, calls) stays default fg + +"string" = { fg = "string" } +"string.regexp" = { fg = "string" } +"string.special" = { fg = "string" } + +"constant" = { fg = "constant" } +"constant.numeric" = { fg = "constant" } +"constant.character" = { fg = "constant" } +"constant.builtin" = { fg = "constant" } + +"comment" = { fg = "comment" } +"comment.line" = { fg = "comment" } +"comment.block" = { fg = "comment" } + +"function" = { fg = "definition" } +"function.builtin" = { fg = "definition" } +"function.method" = { fg = "definition" } + +"constructor" = { fg = "definition" } +"type" = { fg = "definition" } +"type.builtin" = { fg = "definition" } + +# These are NOT highlighted (Alabaster philosophy: keywords are obvious) +"keyword" = { fg = "fg" } +"keyword.control" = { fg = "fg" } +"keyword.operator" = { fg = "fg" } +"variable" = { fg = "fg" } +"variable.parameter" = { fg = "fg" } +"variable.builtin" = { fg = "fg" } + +# Punctuation is dimmed +"punctuation" = { fg = "punctuation" } +"punctuation.bracket" = { fg = "punctuation" } +"punctuation.delimiter" = { fg = "punctuation" } + +"operator" = { fg = "punctuation" } + +# Special cases +"tag" = { fg = "definition" } +"tag.error" = { fg = "error-red", underline = { style = "line" } } +"attribute" = { fg = "fg" } +"namespace" = { fg = "definition" } +"label" = { fg = "constant" } + +# MARKUP - For markdown/documentation +"markup.heading" = { fg = "definition", modifiers = ["bold"] } +"markup.list" = { fg = "fg" } +"markup.bold" = { modifiers = ["bold"] } +"markup.italic" = { modifiers = ["italic"] } +"markup.link.url" = { fg = "string", modifiers = ["underlined"] } +"markup.link.text" = { fg = "definition" } +"markup.quote" = { fg = "comment" } +"markup.raw" = { fg = "string" } + +# DIFF - Version control +"diff.plus" = { fg = "string" } +"diff.minus" = { fg = "error-red" } +"diff.delta" = { fg = "highlight" } + +[palette] +# Core colors (Alabaster-inspired) +fg = "#000000" # Main text (Alabaster uses pure black) +bg = "#F7F7F7" # Background (Alabaster's light grey) + +# The 4 semantic colors +string = "#448C27" # Green - strings & numbers +constant = "#7A3E9D" # Magenta - constants, booleans +comment = "#AA3731" # Red - comments (important!) +definition = "#325CC0" # Blue - function/class definitions + +# Supporting colors +punctuation = "#777777" # Grey - dimmed operators/brackets +selection = "#DDE7ED" # Light gray-blue - secondary selections (subtle but distinct) +selection-primary = "#BFDBFE" # Light blue - primary selection (original Alabaster) +active = "#007ACC" # Bright blue - cursor, active elements +highlight = "#FFBC5D" # Orange - search, warnings +error-red = "#AA3731" # Red - errors +panel = "#EEEEEE" # Darker grey - UI panels, menus, popups +cursorline = "#EFEFEF" # Subtle highlight - cursorline, ruler +jump-label = "#FF4500" # Bright orange-red - jump destinations +inlay-hint = "#8090B8" # Dimmed blue - virtual text (type hints) + +# Diff colors +diff-green = "#448C27" # Green - additions (same as string) +diff-red = "#AA3731" # Red - deletions (same as error-red) +diff-orange = "#FFBC5D" # Orange - changes (same as highlight) |
