It is interesting to note that adding the options is all we need to do here,
the machinery is such that these options will be taken into account
automatically when set.

1 patch for repository http://darcs.net/screened:

patch 4b741509ef5539aba0d9f03d93b24e13e5d4706a
Author: Ben Franksen <ben.franksen@online.de>
Date:   Fri Mar 10 12:41:16 CET 2023
  * diff command: support --look-for-moves and --look-for-adds options

  This is useful when using `darcs diff` with unrecorded changes.
  (Note that --look-for-replaces makes no sense for diff.)

Attachments

• diff-command_-support-__look_for_moves-and-__look_for_adds-options.dpatch
• patch-preview.txt

Will self-accept but not immediately. IMO this is a no-brainer and 
adds useful functionality at no price at all.

What does `--look-for-moves` mean for diff? Doesn't it end up displaying
them as a delete/add combo anyway?

Yes it does. It's not extremely useful, but can come in handly, for 
instance, to produce a (standard, UNIX) patch file.

> Yes it does. It's not extremely useful, but can come in handly, for
> instance, to produce a (standard, UNIX) patch file.

What I'm not seeing is how the output or behaviour with `--look-for-moves` 
differs from if you run with `--look-for-adds`?

With --look-for-moves you get the diffs for precisely the files that 
you renamed plus whatever it would show without the option. With --
look-for-adds you get the diffs for every (non-boring) file that 
happens to exist in your repo.

Ah, I see. Thanks.