When you use darcs move on a non-repository path, it gives funny error
messages. Some examples (with darcs 2.4.98.5) from the darcs darcs repo:

===
$ darcs move GNUmakefile /var/lib
Ignoring non-repository paths: /var/lib
darcs: Cannot rename a file or directory onto itself!

$ darcs move GNUmakefile dontexist /var/lib
Ignoring non-repository paths: /var/lib
darcs failed:  The target directory dontexist isn't known in working
directory, did you forget to add it?

$ darcs move GNUmakefile src /var/lib
Ignoring non-repository paths: /var/lib
$ darcs wh
move ./GNUmakefile ./src/GNUmakefile
===

This happens because darcs move does not expect that the fixSubPaths
function returns a list that is shorter than its argument. That case
occurs when you supply non-repository paths (on darcs without patch404
these have to be absolute).

Observation: this is another funny interaction between throwing out 
paths and assuming the last good path is the target.

I guess we need an exception to explicitly catch the last path (not just 
the last good one) being a bad path so that we get less funny UI.

Trade-off between code complexity and helpful UI

The following patch sent by Reinier Lamers <tux_rocker@reinier.de> updated issue issue1965 with
status=resolved;resolvedin=2.8.0 HEAD

* resolve issue1965: Resolve conflicts with argument handling work in move 
Ignore-this: 7d12c75a4806cb786d118a3cb64f8904

This resolves conflicts with:
Wed Mar 17 00:02:11 EET 2010  Alexey Levan <exlevan@gmail.com>
  * Separate argument handling from repository work in Move.lhs