I ran some quick tests...
All you've demonstrated is that the cmd.exe built-in command "dir" uses / for processing arguments, as documented
$ "C:/MinGW/msys/1.0/bin/dir.EXE" asdf "C:/MinGW/msys/1.0/bin/dir.EXE": asdf: No such file or directory $ "C:\MinGW/msys/1.0/bin\dir.EXE" asdf "C:/MinGW/msys/1.0/bin/dir.EXE": asdf: No such file or directory $ C:\MinGW/msys/1.0/bin\dir.EXE asdf /usr/bin/dir: asdf: No such file or directory $ C:\MinGW/msys/1.0/bin\dir.EXE\$HOME asdf The directory name is invalid. $ C:\MinGW/msys/1.0/bin\dir.EXE\blah.exe The directory name is invalid.
This 8.3 naming stuff is "bad juju".
Yup, that is why there is NtfsDisable8dot3NameCreation, but it does have benefits
8.3 saves you the trouble of quoting paths in the shell, say for batch files and the like
8.3 spares you the headache of dealing with broken programs that don't quote paths they give to the shell, like legacy applications
8.3 spares you the headache of dealing with broken programs that split on whitespace
In reply to Re^2: perl windows backtick problem
by Anonymous Monk
in thread perl windows backtick problem
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |