thoughts on a bzrrc file

[Benno]

On Thu May 19, 2005 at 17:12:46 +1000, Martin Pool wrote:
>Hi,
>
>Continuing an earlier discussion: it seems to make sense to have a
>~/.bzrrc file holding per-user configuraton.  We should possibly move
>the email setting from its own file into the rc file.  The particular
>one I would like to add now is a command to produce diffs using an
>external diff program rather than difflib.
>
>Arch has a directory containing a bunch of single-value files, which
>is kind of nice in a unixy way, but has its limitations.
>
>On Windows it might make sense to use the registry as well/instead.
>
>One option is to just make it a Python file, but that may cause
>confusion to people unaccustomed to Python who make syntax errors.
>
>Another, and probably the best, is to use ConfigParser_ to read a
>.ini-style format, as used by Windows and Samba.  This style of file
>is also used by svn and more recently by baz.
>
>_ http://docs.python.org/lib/module-ConfigParser.html
>
>So:
>
>
>----------------
># my bzr config file
>
>diff_program = diff -uw %s %s
>email = Martin Pool <mbp at sourcefrog.net>
>editor = emacsclient %s
>

How about the option of having a ~/.bzrrc.py file for those that want
to script settings. I think my previous example had setting a different
email based on the project. E.g:

if (project_is_about_work):
  email = me at work
else: 
  email = me at home

Cheers,

Benno