1. Summarise the issue (what were doing, what went wrong?)

On a new system, darcs prompts the user their e-mail address and stores it 
in the _darcs/prefs/author file of the current repository. It does it again 
and again for every new repository.

I observed this annoyed students two years ago when they used darcs (as 
reported in http://darcs.net/Ideas/Education).

2. What behaviour were you expecting instead?

Save e-mail into ~/.darcs/author .

Setting this parameter globally (for the user) is what recommend git and 
mercurial in their help messages, and this is what does bazaar with the 
command "bzr whoami".

I forgot to put darcs-devel as nosy when I created this ticket, so it 
did not appear on the list. Here it is:

1. Summarise the issue (what were doing, what went wrong?)

On a new system, darcs prompts the user their e-mail address and stores 
it 
in the _darcs/prefs/author file of the current repository. It does it 
again 
and again for every new repository.

I observed this annoyed students two years ago when they used darcs (as 
reported in http://darcs.net/Ideas/Education).

2. What behaviour were you expecting instead?

Save e-mail into ~/.darcs/author .

Setting this parameter globally (for the user) is what recommend git and 
mercurial in their help messages, and this is what does bazaar with the 
command "bzr whoami".

The following patch sent by Jose Luis Neder <jlneder@gmail.com> updated issue issue2320 with
status=resolved;resolvedin=2.10.0 HEAD

* resolve issue2320: save prompted author name in ~/.darcs/author instead of ./_darcs/prefs/author 
Ignore-this: b3614c99ca6cfc970229e347fcfafe4c