Skip to content
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

base16/xresource colours not kept during hints and history #1906

Closed
BlueDrink9 opened this issue Aug 13, 2019 · 4 comments
Closed

base16/xresource colours not kept during hints and history #1906

BlueDrink9 opened this issue Aug 13, 2019 · 4 comments

Comments

@BlueDrink9
Copy link

I use base16-shell to change kitty's colours from time to time (usually in the evenings). Since kitty can't source a new colours.conf while running (AFAIK), this is the only option.

When opening the scrollback pager, or opening hints, the colours return to those specified in the config file.

Note, they do return to base16's colours after closing the pager/hinting.

@SolitudeSF
Copy link
Contributor

it can using remote protocol. kitty @ set-colors

@BlueDrink9
Copy link
Author

BlueDrink9 commented Aug 14, 2019

Woah, neat. Still means base16-shell has significantly reduced usefulness, but I'm pleased about this option!
This program gets updated so often it's easy to find you haven't read documentation you thought you had.

@BlueDrink9
Copy link
Author

Yes, this has solved my use-case most of the time, I'll just stick to using actual kitty schemes as much as possible. On that note, a central repo for schemes would be excellent...

However, the problematic behaviour remains, so I'll leave it up to the maintainer as to whether to close the issue.

@Luflosi
Copy link
Contributor

Luflosi commented Aug 14, 2019

There is a central repo for themes, see https://github.com/dexpota/kitty-themes. It even has instructions on how to load the themes without restarting kitty.

When opening the scrollback pager, or opening hints, the colours return to those specified in the config file.

@kovidgoyal is there a way to change this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants