We also have to check the "True" case to make the test relevant.

We have to check for boolean before int, because int is also
a valid boolean.

Older python versions (< 3.x?) do not support item
assignments with config parser instances. We have
to workaround therefore.

By default we should read config files in user
homes.

We can build a sensible list of config file locations on-the-fly.

Right now we consider a file ".diceware" in the users home as
only valid place for a diceware config file.

Travis is not happy without `coverage`. It would be nice if we could
such requirements before commits. Maybe `tox` is the way to go then?
On the other hand it is nice to have different builds in travis.

Travis CI now comes with container infrastructure as shown in
http://docs.travis-ci.com/user/migrating-from-legacy/. Let's give it a
try.

Tell about dash by name.