On Mon, Jan 14, 2013 at 05:04:17PM +0100, Corinna Vinschen wrote: >On Jan 14 10:27, Christopher Faylor wrote: >> On Mon, Jan 14, 2013 at 11:00:02AM +0100, Corinna Vinschen wrote: >> >The first step of converting a POSIX path to a Windows path is to >> >normalize the path. "." and ".." components are simply dropped: >> > >> > "a/b/./c" -> "a\b\c" >> > "a/b/../c" -> "a\c" >> >[...] >> Also: >> >> c:\>dir foo\bar\..\.. >> >> Volume in drive S is share Serial number is e620:3c3d >> Directory of S:\* >> >> 1/11/2013 9:58 <DIR> . >> 12/26/2012 21:34 <DIR> .. >> 1/12/2013 16:27 <DIR> bin >> 1/14/2013 10:20 <DIR> cgf >> ... >> >> I don't have a foo directory but cmd was happy to just ignore that >> fact and show my the root directory. This is YA place where Windows >> and Linux differ drastically. > >Indeed. Before writing my mail I tested the "GetFullPathName" function, >and I was not exactly surprised to find that it behaves as you describe >for CMD.
Right. It's not just CMD. A standard windows program will behave similarly. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple