I'd like to optionally have a mode for files in which hunks break on empty
lines, in order to minimise conflicts on files where paragraphs have semantic
value (be it latex files or haskell files with functions separated by blank lines).

On Sun, Oct 26, 2008 at 12:45:43AM +0000, Florent Becker wrote:
> I'd like to optionally have a mode for files in which hunks break on empty
> lines, in order to minimise conflicts on files where paragraphs have semantic
> value (be it latex files or haskell files with functions separated by blank lines).

What happens when a hunk adds or removes a newline?  This sounds like
a pretty invasive, backwards-incompatible change to me.  Can you think
of a way to make it backwards-compatible?

Note that this would not be a new type of patches, just a modification on how
record generates the hunks. Thus I don't think it would create any
backward-incompatibility: any older darcs to which i send changes sees normal hunks.

This could be triggered by record --paragraphs, but i'd like to be able to state
rules that say for example than any .tex file in my repo should be treated that way.

Would resolving issue126 be good enough?

We need to fight against flag proliferation.  Each flag is a pebble.  Get enough
pebbles and you've got an avalanche (run for your life!).  The ideal is to make
darcs do what everybody wants not by adding more options but by adding just the
right options that they can combine to get the desired effect.

Marking this as wont-fix for now as it seems this would be subsumed by a good
hunk-splitting interface.