From 6cea47858144b6eb694acb028f7bf51b17c3be77 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Sat, 25 Jul 2026 10:25:07 -0700 Subject: [PATCH] Separate Lupine's green from its yellow Both slots held #026fde, so strings and numbers rendered in one color and syntax highlighting lost the distinction entirely. It mattered less when the theme shipped its own nvim and vscode files; now that both generate from this palette, the collision is visible everywhere. The green slot takes a violet. Lupine's hues sit at 210, 214, 224, 267 and 301, leaving one real gap between blue and magenta, and that gap is the only place a new color fits without either crowding an existing hue or breaking the blues-and-purples character. Its bright variant becomes a lavender, which suits a theme named for the flower. Nothing here reads as green; the slot keeps its ANSI name, not its usual hue. Yellow, orange and cyan remain close to each other. Pulling those apart means either warm hues or a wider spread than the theme allows, which is a bigger change than this one. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_018CC9kSQv8ZEogaxDoeKBzL --- themes/lupine/colors.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/themes/lupine/colors.toml b/themes/lupine/colors.toml index 5dc06194..8d12987a 100644 --- a/themes/lupine/colors.toml +++ b/themes/lupine/colors.toml @@ -17,7 +17,7 @@ bright_foreground = "#000000" red = "#c900c4" yellow = "#026fde" orange = "#026fde" -green = "#026fde" +green = "#4a2fd0" cyan = "#0c67de" blue = "#3264eb" magenta = "#8a4ad7" @@ -25,7 +25,7 @@ brown = "#013a6f" bright_red = "#f930fb" bright_yellow = "#358fff" -bright_green = "#358fff" +bright_green = "#9f85e0" bright_cyan = "#3986ff" bright_blue = "#5482ff" bright_magenta = "#b363ff"