summaryrefslogtreecommitdiff
path: root/config/nvim/colors/kanagawabones.lua
diff options
context:
space:
mode:
authorIgor Soarez <igor@soarez.org>2026-10-17 11:07:32 +0100
committerIgor Soarez <igor@soarez.org>2026-10-17 11:07:32 +0100
commit95056eacdff97a710129bbb29e707ab83f5faa72 (patch)
treeef8fe50947e506859bc0190bd777c50f2f666453 /config/nvim/colors/kanagawabones.lua
parentc0771c839df57a627ceb21bd398752ba2b1ed3f1 (diff)
theme-gen: derive tmux and ghostty colours for any theme
`theme --set <mode> <name>` needs a tmux conf and a ghostty colour file that alacritty-format themes do not provide, so such a name fell back to the generic dark/light tmux colours and left ghostty unchanged, exiting 0. bin/theme-gen reads a theme in alacritty .toml format (by alacritty-theme checkout name or path) or Ghostty's bundled `palette = N=#hex` format, and writes config/tmux/colors/<name>.conf and config/ghostty/colors/<name>, plus config/alacritty/colors/<name>.toml for a ghostty-format source. Generated with it: sonokai, solarized_osaka_night, kanagawabones and dracula_plus_high_contrast, with nvim stand-ins for the three that have no nvim port installed. Parsed keys go through eval, so only plain section.key names and hex values are accepted: a theme file could otherwise run commands. From dot request 20261017-110255-work-laptop-48c22c.
Diffstat (limited to 'config/nvim/colors/kanagawabones.lua')
-rw-r--r--config/nvim/colors/kanagawabones.lua5
1 files changed, 5 insertions, 0 deletions
diff --git a/config/nvim/colors/kanagawabones.lua b/config/nvim/colors/kanagawabones.lua
new file mode 100644
index 0000000..58da269
--- /dev/null
+++ b/config/nvim/colors/kanagawabones.lua
@@ -0,0 +1,5 @@
+-- Stand-in for "Kanagawabones" (selected via bin/theme): no bones nvim port
+-- is installed yet, so use the closest installed dark theme rather than have
+-- `colorscheme kanagawabones` error at startup. Swap when a port is added.
+vim.opt.background = "dark"
+vim.cmd("colorscheme onedark")