Repository navigation
boo-schnickle is broken in all repositories #114
Description
Recently the strings were changed for boo-schnickle. In every single child repository, the names are wrong. Its impossible to use this scheme. Issue introduced here: #109
$ tinty apply base16-booshnickle-dark
Error: Failed to apply theme "base16-booshnickle-dark"
Caused by:
Scheme does not exist: base16-booshnickle-dark
$ tinty apply base16-boo-shnickle-dark
Theme does not exists for tinted-shell in ~/.local/share/tinted-theming/tinty/repos/tinted-shell/scripts. Try running `tinty update` or submit an issue on https://github.com/tinted-theming/tinty
Theme does not exists for base16-vim in ~/.local/share/tinted-theming/tinty/repos/base16-vim/colors. Try running `tinty update` or submit an issue on https://github.com/tinted-theming/tinty
Theme does not exists for tmux in ~/.local/share/tinted-theming/tinty/repos/tmux/colors. Try running `tinty update` or submit an issue on https://github.com/tinted-theming/tinty
Theme does not exists for tinted-terminal in ~/.local/share/tinted-theming/tinty/repos/tinted-terminal/themes/ghostty. Try running `tinty update` or submit an issue on https://github.com/tinted-theming/tinty
Theme does not exists for tinted-wezterm in ~/.local/share/tinted-theming/tinty/repos/tinted-wezterm/themes/wezterm. Try running `tinty update` or submit an issue on https://github.com/tinted-theming/tinty
Theme does not exists for tinted-fzf in ~/.local/share/tinted-theming/tinty/repos/tinted-fzf/sh. Try running `tinty update` or submit an issue on https://github.com/tinted-theming/tinty
Theme does not exists for tinted-lazygit in ~/.local/share/tinted-theming/tinty/repos/tinted-lazygit/themes. Try running `tinty update` or submit an issue on https://github.com/tinted-theming/tinty$ tinty list | grep boo
base16-boo-shnickle-dark
base16-boo-shnickle-light$ cd .local/share/tinted-theming/tinty/repos/tmux/colors && fd boo
base16-boo-shnickle-light.conf
base16-boo-shnickle.conf
base16-booshnickle-dark.confTo get this scheme working again, heres is what I have done for now:
mv ~/.local/share/tinted-theming/tinty/repos/tinted-shell/scripts/base16-booshnickle-dark.sh ~/.local/share/tinted-theming/tinty/repos/tinted-shell/scripts/base16-boo-shnickle-dark.sh
mv ~/.local/share/tinted-theming/tinty/repos/tinted-terminal/themes/ghostty/base16-booshnickle-dark ~/.local/share/tinted-theming/tinty/repos/tinted-terminal/themes/ghostty/base16-boo-shnickle-dark
mv ~/.local/share/tinted-theming/tinty/repos/tinted-wezterm/themes/wezterm/base16-booshnickle-dark.toml ~/.local/share/tinted-theming/tinty/repos/tinted-wezterm/themes/wezterm/base16-boo-shnickle-dark.toml
mv ~/.local/share/tinted-theming/tinty/repos/tinted-fzf/sh/base16-booshnickle-dark.sh ~/.local/share/tinted-theming/tinty/repos/tinted-fzf/sh/base16-boo-shnickle-dark.sh
mv ~/.local/share/tinted-theming/tinty/repos/tinted-lazygit/themes/base16-booshnickle-dark.yml ~/.local/share/tinted-theming/tinty/repos/tinted-lazygit/themes/base16-boo-shnickle-dark.yml
mv ~/.local/share/tinted-theming/tinty/repos/base16-vim/colors/base16-booshnickle-dark.vim ~/.local/share/tinted-theming/tinty/repos/base16-vim/colors/base16-boo-shnickle-dark.vim
mv ~/.local/share/tinted-theming/tinty/repos/tmux/colors/base16-booshnickle-dark.conf ~/.local/share/tinted-theming/tinty/repos/tmux/colors/base16-boo-shnickle-dark.conf
mv ~/.local/share/tinted-theming/tinty/repos/tinted-yazi/flavors/base16-booshnickle-dark.toml ~/.local/share/tinted-theming/tinty/repos/tinted-yazi/flavors/base16-boo-shnickle-dark.toml
mv ~/.local/share/tinted-theming/tinty/repos/tinted-claude-code/scripts/base16-boo-shnickle.js ~/.local/share/tinted-theming/tinty/repos/tinted-claude-code/scripts/base16-boo-shnickle-dark.js
Activity
JamyGolden commentedon Jul 19, 2026
It looks like this is where the issue comes from, the author of the scheme renamed it: 5f868b3. Have you run
tinty updateortinty sync?nathandaven commentedon Jul 19, 2026
@JamyGolden yep, it is reproducible on a fresh install, the child repositories still have the old strings, doesn't seem the ci has picked up the change
JamyGolden commentedon Jul 20, 2026
Ahh right I know what the issue is. The builder is adding newly built schemes, but not removing old schemes, so there are more themes in the templates than there are schemes in the schemes repo. I'll fix it so the builder cleans out the old files. So
base16-booshnickle-darkandbase16-boo-shnickle-darkexist in the template repos, but tinty doesn't seebase16-booshnickle-darkas existing since it's looking at what exists in the schemes repo.nathandaven commentedon Jul 20, 2026
Awesome! Thanks for taking a look :)
nathandaven commentedon Sep 17, 2026
@JamyGolden any update here?
JamyGolden commentedon Sep 23, 2026
Hey, I'd partially built a feature to fix it and forgot about it. I've just created a pull request for tinted-builder-rust which we can use to fix the issue on our templates
jjb commentedon Oct 17, 2026
cc @JamyGolden. Status of the leftover-file fix as of 2026-10-18:
build --prunewas added to tinted-builder-rust in Add--pruneflag to prune unrecognised files in generated dir tinted-builder-rust#42 and Fix--prunedeleting unrelated files tinted-builder-rust#43, both merged. It isn't in a release yet: the latest is v0.21.0 (2026-06-15), and the update workflows install the latest release.--pruneyet. home'sshared-build-template-and-commit-themes.ymlrunstinted-builder-rust build .. tinted-sublime-text doesn't use the shared workflow; its ownupdate.ymlruns the same command. Code search found no other repo with its own build step.Remaining steps:
--prune.tinted-builder-rust build .totinted-builder-rust build . --prunein home'sshared-build-template-and-commit-themes.ymland in tinted-sublime-text'supdate.yml.The next scheduled update in each repo would then delete the leftover files. Leftover files today, from comparing a fresh build of current schemes with what's committed:
base16-booshnickle-dark.base16-booshnickle-dark. They still appear in Sublime's theme picker.🤖 Generated with Claude Code