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
Allow variable substitution in --color-muted #80
Comments
I think |
I'm not sure if that's the 'canonical' way that polybar does it, but yeah in my polybar config, i have a block such as
which just renames the xrdb variables to something more palatable, and then when i want to use it, for example
this works for the polybar modules i'm using so far, so maybe the best option would be Thanks for the quick response and the amazing module btw :) |
That won't work because polybar variables can't be set as part of another string. If you use a variable, the entire value has to be the variable, not |
I'm just trying to achieve something similiar to, for example, the default PulseAudio module, see https://github.com/rtreccani/dotfiles/blob/newlap/polybar/config#L168. Forget using Pywal, is it possible to statically set the colour of unmuted vs muted? |
I use wal to theme my system, and for most modules I could use something like
format-muted = ${colors.disabled}
to make the module highlight red when muted, or use--color-muted ${colors.disabled}
in my call to the pulseaudio-control bash script, but I get/bin/bash line 1: bad substitution
when I do that.Is there an undocumented way to change the color of the module when muted, or some way to correctly escape the color such that it can be read?
The text was updated successfully, but these errors were encountered: