Closed alexveden closed 6 months ago
BTW, when I was working on layout module, it seems there are 2 layout.py
in core and contrib dirs. Bumblebee-status picks the contrib verison, I don't know if this is an issue or intentional. Maybe more clarity is required in the docs.
Oh, I did not notice the issue regarding duplicate module names, I will certainly investigate that. Thanks for mentioning this and thanks for the cool PR!
This might be functionality that could be nice in the framework itself - add a highlight group if a widget does (not) have a certain value.
This pull request introduces a new option for highlighting non-default layout:
Does the following: Default layout![image](https://github.com/tobi-wan-kenobi/bumblebee-status/assets/18488560/61c8c42a-ec5c-44e7-b963-6bde7d67093c)
Non-default;![image](https://github.com/tobi-wan-kenobi/bumblebee-status/assets/18488560/c6b334f6-d32e-45e9-a676-e57996e7eed5)
Previous plugin behavior preserved, if option not set, no highlighting for both layouts.