.bzrrc file [ was Re: Slow startup?]

[Benno]

On Sat Apr 16, 2005 at 02:43:12 +1000, Benno wrote:
>On Fri Apr 15, 2005 at 11:43:41 +1000, Robert Collins wrote:
>>On Fri, 2005-04-15 at 11:39 +1000, Martin Pool wrote:
>>> Thanks for the report.
>>> 
>>> I've taken out the fqdn call and now just use gethostname, which should
>>> be reliably fast.  I also take a username from ~/.bzr.email if it
>>> exists, which should be easy for people on all platforms to set.
>>> 
>>> Having a long real time but a short user+sys is often a dead give away
>>> of a DNS or other network timeout, because it shows the program spends a
>>> long time just waiting.
>>
>>it would be good to stash all global config in ~/.bzr, rather than
>>having a bunch of files in ~.
>
>I agree, I think I wrote this email on the plane, and then forgot to send it:
>
>1/ Global arguments:
>
>Should we have global arguments ala CVS? For example
>some that I think should be global currently would be:
>
>-u Username
>-v Verbose
>-e Editor
>
>At the same time having a .bzrrc would also be useful. E.g:
>
>"""
>-e emacs
>-u Ben Leslie <benno at benno.id.au>
>diff -u
>"""
>
>Should .bzrrc be some like .cvsrc, or should it just be a
>python file. I like the python file option. Then I can have
>something like:
>
>if commit_repo_is_for_work:
> username = "Ben Leslie <Ben.Leslie at nicta.com.au>"
>else:
> username = "Benno <benno at benno.id.au>"

Reading some other threads going at the moment, another advantage of
having a pure python startup file is that users could add their own
command aliases and the such.

Cheers,

Benno