fossil mv nonexistentfile newfilename

I expect, that fossil will refuse that command.

dmitry added on 2011-10-24 18:15:59 UTC:
I think leaving it as is, issuing a warning, or asking a user to confirm the action instead of failing is better, because I sometimes first do

mv file renamedfile

and then remember to mv it in Fossil:

fossil mv file renamedfile

If Fossil didn't allow this, I'd have to rename the file back to the original name, then do `fossil mv`, and rename it again.