Works only with the new version of wallchanger.
Does not do any resolution checks, so you will get a random image which
might not really fit your resolution. It's fallback after all :)
i3bar_wrapper.bash now takes the conkyrc for the status line as the
first argument so host specific conkyrcs can be used. Additionaly, the
conkyrcs for virtualarch and netbook were updated. Virtualarch has
hardly changed, but netbook now has a quite short statusline that fits
the screen size.
It's now conky -> i3bar. To enable colors, conky produces JSON output.
The script i3bar_wrapper.bash handles the invocation of conky and
redirects the output of i3bar to i3bar_clickparser.bash, in which click
events can be handled (none implemented right now).
conky/virtualarch.conky.dzen is a conky output suitable for dzen2, it
should produce the same output as conky/virtualarch.conky does with
i3bar and JSON.
The script genconfig.bash concatenates the main configuration file with
a host specific one to create a session-specific configration file that
is then passed to i3. It therefore has to be called in .xinitrc or
something comparable before starting i3. If no host specific
configuration is found, a default file will be used instead. This is
useful for providing default that should not go into the main
configuration file, maybe because they are incompatible with some host
specific settings. For example a default bar{} block goes there, as if
this was in the main config, two i3bar instances would be started when a
host specific config specifies its own.
The script genconfig.bash concatenates the main configuration file with
a host specific one to create a session-specific configration file that
is then passed to i3. It therefore has to be called in .xinitrc or
something comparable before starting i3. If no host specific
configuration is found, a default file will be used instead. This is
useful for providing default that should not go into the main
configuration file, maybe because they are incompatible with some host
specific settings. For example a default bar{} block goes there, as if
this was in the main config, two i3bar instances would be started when a
host specific config specifies its own.
