Re: Forward slashes in path and pipes

Andrew DeFaria wrote: >> For some reason (the presence of the pipe?) cmd.exe parses the forward >> slash as an options separator rather than a path component in one case >> but not the other. Quoting removes the ambiguity. > Yes, my Cygwin question would be why does it store "/" in the registry > f

Re: Forward slashes in path and pipes

Dave Korn wrote: Andrew DeFaria wrote: Found out a funny thing about Cygwin today. I've known for a while that forward slashes works as well as backslashes when specifying a path to execute. So all of the following work from a cmd prompt: C:> C:\Cygwin\bin\ls C:> C:\Cygwin/bin\ls C:> C:/Cygwi

Re: Forward slashes in path and pipes

Andrew DeFaria wrote: > Found out a funny thing about Cygwin today. I've known for a while that > forward slashes works as well as backslashes when specifying a path to > execute. So all of the following work from a cmd prompt: > > C:> C:\Cygwin\bin\ls > C:> C:\Cygwin/bin\ls > C:> C:/Cygwin/bin/ls

Forward slashes in path and pipes

Found out a funny thing about Cygwin today. I've known for a while that forward slashes works as well as backslashes when specifying a path to execute. So all of the following work from a cmd prompt: C:> C:\Cygwin\bin\ls C:> C:\Cygwin/bin\ls C:> C:/Cygwin/bin/ls Also the following works: C:>