global color_bad about i3blocks HOT 7 CLOSED

+1 for this feature, this could be really useful.

from i3blocks.

+1 I made something like this in #90, which let you set a custom color when you exit with urgent, but i3bar almost immediately updated to break it.

from i3blocks.

I would like to see this in the i3 config with the rest of the bar colors.

from i3blocks.

Feel free to modify the included iface script. Just change line 38:

echo \#FF0000 # color

The included scripts give a great starting point but i3blocks has always aimed primarily to provide a simple framework for writing custom scripts and a set of commonly used example scripts to get started. If you haven't done so, consider copying the scripts to something like ~/bin/i3blocks/ so you can modify them as desired.

A custom down colour would better meet people's needs but would require adding a flag or option to the script; something that the project is trying to avoid. Adding options means more documentation and a messier example config to demonstrate what is possible.

A global isn't actually possible given i3blocks' architecture. i3blocks is a very thin codec between STDOUT and i3bar.json. Each parameter maps identically to an i3bar protocol field. For example, this is why a custom separator isn't possible (however, the i3bar config section has an option to change this). i3bar implements this so the best that can be done given the protocol is to turn off the separator for every block and add a block for each separator. Same with urgent colour. The protocol only allows us to send a true or a false for urgency (not a colour, font scheme like underlining or bold, or a message for libnotify).

Oh, a few people want to know how to set a custom urgent colour. i3bar uses the style provided by the i3 config bar{colors{urgent_workspace}} command.

Just modify the following (border isn't used by i3bar):

bar{
    ...
    colors{
        ...
        # class          border  backgr. text
        urgent_workspace #dc322f #dc322f #eee8d5
}}

from i3blocks.

Thank you very much!

from i3blocks.

Note that this obviously also changes the way urgent workspace buttons look.

The name urgent_workspace isn't entirely correct anymore due to this, but introducing a separate directive for it would have been overkill. And anything else isn't compatible with previous versions.

from i3blocks.

I'm closing this issue since such an option would diverge too much from the i3bar protocol. Thanks for your input on the issue guys!

from i3blocks.