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

[Andreas Schwab <schwab@suse.de>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> In your case, the patch specifies two files which diff-mode can both find,
> yet, the patch is not between those two files (at least in your test case,
> the two files are just the same, presumably one being a "working tree" and
> the other being basically unrelated).

The patch is relative to an older version of the file, my intention was to
find out which parts of it have already been applied, and apply those that
aren't (and some hunks need editing to apply, so I couldn't just ignore
the rejects).

> Is your test case very representative, or are there many other different
> cases where you bump into the same problem?

It's actually the first time I used that feature.  For me this behaviour
was very confusing, even before I read the doc string of diff-apply-hunk.
Especially more so because it also automatically moves forward so that the
effect is not immediately visible.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."