Try this on a case insensitive system:

darcs init
touch foo
darcs add FOO
cat _darcs/prefs/patches/pending

Notice that it lets you use the wrong case in a record

It should probably have some way of noticing that while file "FOO" is actually
supposed to be called "foo".  And it should warn you that you are potentially
doing something silly.

Note that this might be related to other case-sensitivity bugs like issue234
(which I have been unable to reproduce lacking the exact 'recipe')

I'll bet that implementing this is easy (just a check in Add.lhs. I'm not sure
what to call the switch for this; maybe extending --case-ok will be good)

This "wish" seems to be saying that darcs should care about what case a file is,
even on file systems that don't care. (And maybe it should because darcs
projects can be cross-platform). 

However, I don't see how you can use a "wrong case in a record" when according
to the filesystem, either case is correct. 

I'm comfortable with resolving this as "not-our-bug", considering we already
have "--case-ok" to partially address this issue, and case-sensitivy issues are
improved some Darcs2 and the new repo format.

I'm not sure what the best semantics for this situation would be.  Eric's
suggestion isn't bad:  warn when darcs' view of the case of a file differs from
what's in the working directory.  I think we could do this in coslurp without
too much trouble.  I'm not sure how worthwhile it is, though.

David

I guess this isn't worth the trouble.