Please ship example config file separately from source

[GoogleCodeExporter]

e.g. /etc/clamz.config, and have clamz read it.

This means two instant advantages:

1. clamz has site-wide config.

2. Users have a visible example. If clamz is installed from a distro (e.g. 
Ubuntu in my case), then there's no source, so no example config file (except 
buried in the binary, with no way to get it out).

As a small aside, an example of putting a shell variable in the config file 
(like ${HOME}), would be nice, as it's not clear from the default settings that 
these use the same syntax as clamz's own format variables.

Original issue reported on code.google.com by reubenrh...@gmail.com on 24 Nov 2010 at 10:30

[GoogleCodeExporter]

It is completely unclear how one is supposed to use the config file:
$HOME/.clamz/config
General configuration file, providing default settings for the  --output,  
--forbid-chars,  --allow-uppercase  and --utf8-filenames options.

Do I put:
--output=$HOME/Music/${artist_album}/${album}
or
output=/home/username/Music/${artist_album}/${album}
?
and how, exactly, do I get Firefox to actually use clamz? The link in the man 
page doesn't seem to make Firefox start using clamz at all.

Original comment by mobiledi...@gmail.com on 30 Nov 2011 at 6:17