Re: diff-apply-hunk documentation doesn't match implementation

[Stefan Monnier]

> The doc string of diff-apply-hunk says:
>   By default, the new source file is patched, but if the variable
>   `diff-jump-to-old-file' is non-nil, then the old source file is
>   patched instead

> But the implementation then goes on to do the opposite:

>       ;; If REVERSE go to the new file, otherwise go to the old.
>       (diff-find-source-location (not reverse) reverse)

This is just one part of the implementation.  The behavior is actually
pretty subtle (too subtle, admittedly).  So I can't judge without knowing
which end-user-level behavior you're referring to.

I.e. give me a recipe.


        Stefan