Use list particles to change font and/or color¶

The string particle, for example, cannot change font or colors in the middle of its string. To do this, you need to wrap multiple string particles in a list particle.

This can be useful if you want to use an icon font for a glyph since the default fallback fonts provided by fontconfig may not favor your icon font.

Also remember there is a short version for lists (see yambar-particles(5))

For example, to render backlight as " 20%", you could use:

content:


  - string:


      font: Font Awesome 6 Free:style=solid:pixelsize=14


      text: 


  - string:


      font: Adobe Helvetica:pixelsize=12


      text: "{percent}%"

Use map particles to handle 'state'¶

Several modules have a state tag that can be used to render different particles depending on the module's state.

For example, you might want different things to be shown for a network interface that is down or up. You could further differentiate between an up interface that has or has not an IP address assigned to it.

Below is an example, where a wired connection is not renderer at all when disconnected.

When connected, it is rendered in the default text color if it is up and also has an IPv4 address. If it is up, but does not have an IPv4 address, it is rendered in a semi-transparent white color.

Finally, if it is down, or in any other unknown state, it is rendered in red.

content:


  map:


    conditions:


      ~carrier: {empty: {}}


      carrier:


        map:


          default: {string: {text: , font: *awesome, foreground: ffffff66}}


          conditions:


            state == up:


              map:


                default: {string: {text: , font: *awesome}}


                conditions:


                  ipv4 == "": {string: {text: , font: *awesome, foreground: ffffff66}}

Use yaml anchors¶

You often end up using the same definitions in a lot of places. This is particular true for fonts. But it can also be true when mapping state.

In these cases, you can define an anchor point, either at top-level, or in a module's anchors attribute:

awesome: &awesome Font Awesome 6 Free:style=solid:pixelsize=14

Then reference it in your particle definitions:

content:


  string: {text: , font: *awesome}