-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Setting theme with +kitten themes produces empty current-theme.conf #6191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Works for me with mv ~/.config/kitty /tmp && kitty +kitten themes duckbones && cat ~/.config/kitty/current-theme.conf&& rm -rf ~/.config/kitty && mv /tmp/kitty ~/.config The duckbones theme is displayed, as expected. |
I overlooked a major detail, sorry for being sloppy: I forgot I have It seems only overwritten and custom themes are affected. When running But by
the same thing happens as described in the issue. After removing PS: I noticed that the name in the comment header in a theme file (
|
Same. The switching with user-defined themes is broken and I end up with an empty |
Yeah I'm having this issue too. |
I'm confirm this bug! The strange thing is that it was working normally. But today after an update no more. |
There's no need to add "me too"s. This issue was closed because it was fixed by Kovid. So you can expect the fix in the next release. |
Setting color theme/scheme using
kitty +kitten themes
does not work since 0.28.0, it only produces an emptycurrent-theme.conf
.To Reproduce
kitty +kitten themes
m
~/.config/kitty/current-theme.conf
has been created~/.config/kitty/kitty.conf
now contains this:The same happened with a different theme and when directly specifying a theme:
kitty +kitten themes duckbones
Environment details
I tried it on Linux (Gentoo, sway) and macOS, each with my custom config and a completely empty
~/.config/kitty/kitty.conf
.The text was updated successfully, but these errors were encountered: