-
Notifications
You must be signed in to change notification settings - Fork 302
More flexible theme config #118
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
Conversation
|
Hi @daschw, thanks for your interests in this project and the effort you put in making this PR. I'll take a look and review this PR the next few days. |
aome510
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is easier to review than I initially thought. Generally, it LGTM. Only a few small changes are needed.
Tried your theme and it also works for me! |
|
Hi, thanks for the review! I implemented all your suggestion. I was not sure, where exactly to put the default 'fg' and 'bg' value description instead of the "border comment". Let me know, if this is not what you had in mind. |
aome510
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes. LGTM!
|
I also update the example theme and |
Hi, thanks for this awesome piece of software!
I just recently came across this project and played around with the theme config a little. At some point I thought it would be nice to have darker borders. However, I could not find this option anywhere in the component styles. So I thought I'd try to implement this myself. After I had finished, I realized that this would require every user to update their theme.toml files because without the new
borderoption spotify_player would not be able to parse them and error. Furthermore I saw that you recently refactored the theming config and deletedfg_selectedandbg_selected(or how they were called) and I saw the TODO comment to find a solution to not having to set each component style when adding this section in theme.toml.Hence I thought, before I add an option to change the border I'll try to figure out a way to solve this TODO. Afterwards, adding new component styles would not be an issue, because it would not affect older configs, that did not set this attribute. So that is what I ended up doing. With this PR
borderselectionI am quite sure that none of these changes affect any existing theme configs.
With this I could now have a theme.toml like this
that would look like this with my terminal colors: