thoughts on a bzrrc file

[Martin Pool]

On 19 May 2005, Magnus Therning <magnus at therning.org> wrote:

> >One option is to just make it a Python file, but that may cause
> >confusion to people unaccustomed to Python who make syntax errors.
> 
> What would the purpose be of using a Python file? More complex
> configurations? (E.g. if in projectA: diff=difflib else: diff=diff ?)

Yes, that sort of thing; sometimes it's useful to have a
Turing-complete configuration language although often (and
particularly with Lua, it seems) it indicates the configuration
variables are not the right ones.

> Is it worth the extra hurdle for non-Pythonites?

I don't think so.  Being able to write plugins if you want them =good;
needing to learn Python to get stuff done =bad.

> Would it take bzr in the direction of monotone's use of Lua?

I don't want to go that way.

> ConfigParser does support the [...] thingie, right?
> That means that external commands thrown into the BZRPATH can use the
> same config file and still it'll be easy to see what belongs to real bzr
> and what's part of "other commands".

Yes.

-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050519/5c8f7a2e/attachment.pgp