thoughts on a bzrrc file

[Magnus Therning]

On Thu, May 19, 2005 at 05:27:51PM +1000, Benno wrote:
>On Thu May 19, 2005 at 17:12:46 +1000, Martin Pool wrote:
[..]
>>----------------
>># 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

Is there some other (non-programming) way of adding per-project
settings?

First I was thinking of personal defaults in ~/.bzrrc and per-project in
the working area but for obvious reasons that wouldn't be very good.

Maybe it'd be possible to put several config files in ~/.bzr/?
For projectA we'd first load ~/.bzr/bzr.conf and then let things in
~/.bzr/projectA.conf override... I guess I should put some code behind
all this rambling instead.

/M

-- 
Magnus Therning                    (OpenPGP: 0xAB4DFBA4)
magnus at therning.org
http://magnus.therning.org/

Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.

I'd doubt that it represents a threat to anything but the notion that you can
sell bad code by refusing to let anyone see what's in the box.
     -- Amy Wohl on Linux and Open Source
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050519/2f21e365/attachment.pgp