On Mon, Nov 12, 2012 at 1:13 PM, Johan Corveleyn <jcor...@gmail.com> wrote: > Hm, I don't see this problem with "cd" in cmd.exe.
No, the problem is only with powershell, but I do believe powershell does what it is designed to do in this case. It uses a unified location system for more things than just filesystems (you can cd into the registry, LDAP etc) and some of them are case sensitive so it preserves the user's typed string. The problem is also with the Set-Location cmdlet, the old, default "cd" command in powershell. Powershell contributes to this problem a bit more; in powershell you can tab-expand the path names. If you just tab-expand one directory at a time, it changes to the correct case of it. But if you write two directories at once (ie apa\Banana), only the second directory gets changed into the correct case. With a longer path and a single letter with the incorrect case, then it is of course a lot less obvious what is wrong. >From a usability point of view, this should be fixed in subversion as windows (and most OSX users) expect that the file names should be case insensitive and other uses of subversion work correctly when the wrong case is used, ie: PS C:\temp\WC> svn mkdir APA A APA PS C:\temp\WC> svn mkdir apa\banan A APA\banan At the very least the error message should suggest a fix. /Sebastian -- One laptop per child project: http://laptop.org/
