Comment 2 for bug 315399

This happens in practice VERY often. Image that x is "{" and y is "}" and you've just described how bzr often gives terrible diffs for changed C++ code, etc. This happens in many other situations as well.

One workaround is to use --using= and point to an external diff command, but a better solution would be so update bzr's diff algorithm to do whatever other diff tools (like GNU diff) are doing that make them work so much better.

For bonus points, it'd be nice if bzr's diff did whatever GNU diff's --minimal does, since that's even better for interactive use.