Re: weird diff output?

Jacob Keller [off-list ref] writes:

On Tue, Mar 29, 2016 at 11:16 AM, Stefan Beller [off-list ref] wrote:

quoted

...
To find a heuristic, which appeals both the C code
and the shell code, we could take the empty line
as a strong hint for the divider:

This seems like a good heuristic. Can we think of any examples where
it would produce wildly confusing diffs? I don't think it necessarily
needs to be default but just a possible option when formatting diffs,
much like we already have today.

I earlier said "50% of the time it is correct, you just do not
remember", but such an option with configuration variable would let
somebody interested set it permanently for his daily use of Git, and
it would help him to find out (1) if he sees a "Huh?" division less
(or more) often than he used to, and (2) if it gives a better
division for the same change to view the diff with the plain-vanilla
heuristic.