i3configger 0.7.3

Why?

I3 already has a very nice and simple configuration system. i3configger makes it a bit more malleable by making it possible to send “messages” to your configuration.

How?

You can change any variable you have defined in the configuration by invoking i3configger set <variable name> <new value>.

You can switch between alternative sub configurations (e.g. different color schemes) that conform with a simple naming convention (config.d/<key>.<value1>.conf, config.d/<key>.<value2>.conf, etc.) by invoking e.g. i3configger select-next <key> or i3configger select <key> <value2>.

This is realized by adding a build step that can be triggered by calling i3configger directly or by running it as a watcher process that automatically rebuilds and reloads when source files change or messages are sent.

To get an idea how this works, have a look at the examples and read the docs.

**Full Documentation is here**

Installation

$ pip install i3configger

See docs For more details and different ways of installation.

0.7.3 (Do the right thing) - 2017-06-11

• use actual partials path for initialization instead of assuming that parent of config path == partials path

0.7.2 (Need for speed) - 2017-06-11

• shave off a few hundred precious milliseconds startup time, by moving the very expensive version fetching into a function that is only called, when the version is really needed.

• help the user, when they use a non existing command

• remove unwanted side effects from message

• when config.d already exists, but no i3configger.json exists yet, it is automatically created now

• better examples/tests

0.7.1 (The great packaging adventure begins) - 2017-06-10

Changed

• (internal) vendor in a different inotify library that makes it easier to package for Archlinux

0.7.0 (Better safe than sorry) - 2017-06-10

Changed

• always create a backup of the users files if it does not exist already. Do not clobber it on subsequent builds to make sure you can always go back to your old files if needed, even if they are no external backups or SCM in place.

0.6.0 (Command & Conquer) - 2017-06-10

0.5.3 (KISS) - 2017-06-09

Changed

• de-rocket-science release process

• change description of tool

0.5.2 (Releasing correctly is hard) - 2017-06-09

Fixed

• wrong CHANGELOG :)

0.5.1 (Maybe I should test more) - 2017-06-09

Fixed

• 4 repair watch and daemon mode

0.5.0 (Half way there) - 2017-06-08

0.4.4 (I am not alone) - 2017-06-05

Fixed

• 2 - fails if not using i3status. Fixed by making the refresh call ignore any errors - not nice, just a quick fix.

0.4.3 - (The Curious Incident of the Dog in the Night-Time) - 2017-06-04

0.4.2 (The answer) - 2017-06-03

Basic implementation

• build main config and one or several i3status configs from the same sources

• variables are handled slightly more intelligently than i3 does it (variables assigned to other variables are resolved)

• end of line comments are possible (removed at build time)

• variables in i3status configs are also resolved (set anywhere in the sources)

• reload or restart i3 when a change has been done (using i3-msg)

• notify when new config has been created and activated (using notify-send)

• simple way to render partials based on key value pairs in file name

• simple way to change the configuration by sending messages

• build config as one shot script or watch for changes

• send messages to watching i3configger process

• if i3 -C fails with the newly rendered config, the old config will be kept, no harm done

Note: The format is based on Keep a Changelog and this project adheres to Semantic Versioning.