1 patch for repository http://darcs.net/screened:

patch e1ed3b126134983f223ae0907dad11e2d1dcb3da
Author: Ben Franksen <benjamin.franksen@helmholtz-berlin.de>
Date:   Fri Feb 13 03:17:12 CET 2015
  * beautified error messages for command line and default files

Attachments

• beautified-error-messages-for-command-line-and-default-files.dpatch
• patch-preview.txt
• unnamed

Setting milestone to 2.10, even though, objectively speaking, this is
not essential. However, I think error messages are something that people
take note of, they are an important part of the general impression one
gets when using a tool.

How can we trigger the error messages modified by this patch?

Here is an example. Before the change:

ben@sarun[1]: .../darcs/screened > darcs record -i -a --ask-deps
--no-ask-deps --skip-long-comment --prompt-long-comment
command line
conflicting flags: interactive, all/no-interactive
conflicting flags: ask-deps, no-ask-deps
conflicting flags: skip-long-comment, prompt-long-comment

ben@sarun[1]: .../darcs/screened > 

After the change:

> darcs record -i -a --ask-deps --no-ask-deps 
Error in command line:
 conflicting flags: interactive, all/no-interactive
 conflicting flags: ask-deps, no-ask-deps
ben@sarun[1]: .../darcs/screened > 

See also patch1289.

I have been working on this a bit more and will send a follow-up patch,
explaining what I do here and why.