anchor.diff:  
   CONFIGURATION
   -------------
  -Yabar currently by default accepts configuration from the config file ~/.config/yabar/yabar.conf or using yabar -c [CONFIG_FILE]. The config file should like something like this:
  +Yabar currently by default accepts configuration from the config file '~/.config/yabar/yabar.conf' or using 'yabar -c CONFIG_FILE'. The config file should like something like this:
   
   ----
   bar-list: ["bar1", "bar2", ...];
  
positive.code: 
  LICENSE
  -------
  Yabar is licensed under the MIT license. For more info check out the file 'LICENSE'.
  
  AUTHORS
  ------
  
negative.code: ----------------------
  Each block can have its own command, background, foreground (i.e. font), underline and overline colors, alignment and other options.
  
  * *Execution*: The path to the command (executable or script) to be executed. Yabar consumes the output of the command/script's stdout and shows it on the bar. Example:
  ----
  exec: "date";
  ----
  
  * *Alignment*: Yabar accepts left, center or right alignments. Consecutive blocks will be placed to the right of each other. Example:
  ----
  align: "right";
  ----
  
  * *Justify*: By default yabar centers the text inside the block size. However, you can optionally justify the text to the left or the right.
  ----
  justify: "left";
  ----
  
  * *Type*: The block type can be *periodic* where the command is executed within a fixed interval of time, *persistent* where the command runs in a persistent way like 'xtitle' or *once* where the command is executed only once where the intended info should not change like in 'whoami'. Examples:
  ----
  type: "periodic";
  type: "persist";
  type: "once";
  ----
  
  * *Interval*: In seconds. This is only useful when the block type is *periodic*. Example:
  ----
  interval: 3;
  ----
  
  * *Fixed size*: You should define the fixed width size of the block. Yabar currently only supports fixed widths. You can deduce the appropriate width using trial and error. The current default value is 80 but you are encouraged to override it to a more appropriate value. Example:
  ----
  fixed-size: 90;
  ----
  
  * *Pango markup*: Yabar accepts either true or false without quotes. Default is false. Example:
  ----
  pango-markup: true;
  ----
  
  * *Colors*: A block has 4 kinds of colors. 'Background', 'foreground' which is the font color when pango markup is not used, 'underline' and 'overline'. Colors are accepted in hex 'RRGGBB' and 'AARRGGBB' representations. Note that the values are integers and not double-quoted strings. Examples:
  ----
  foreground-color-rgb: 0xeeeeee;
  background-color-argb: 0x1dc93582;
  underline-color-rgb: 0x1d1d1d;
  overline-color-argb: 0xf0642356;
  ----
  
  * *Button commands*: This option is used to invoke a command/script upon a mouse button press. You have 5 buttons that usually represent left click, right click, middle click, scroll up and scroll down respectively but this may not be the case for everyone. Examples:
  ----
  command-button1: "pavucontrol";
  command-button4: "pactl set-sink-volume 0 +10%";
  command-button5: "pactl set-sink-volume 0 -10%";
  ----
  
  * *Inheritance*: As the config gets larger because you want to add many blocks, you may find yourself adding many identical option values for every added block. This optional entry is added in order to inherit the options from a precedent block into your new block. You can also override the inherited options with new values.
  ----
  inherit: "bar1.block1";
  ----
  
  * *Icons* and *images*: Yabar supports drawing icons and images inside blocks using 'gdk-pixbuf' and 'cairo'. The images are drawn before drawing text so they may act as backgrounds if desired. You can control the horizontal and vertical shift and the width and height scale for the image/icon. Example:
  ----
  image: "/usr/share/icons/Numix/16/apps/google.svg";
  image-shift-x: 2; #integer value
  