Joe Makowiec wrote: > On 16 Feb 2013 in soc.genealogy.computing, Ian Goddard wrote: > >> Actually it was Cygwin http://www.cygwin.com/ I was thinking of. >> It's a long time since I used it (much easier these days to just run >> Linux) but IIRC it provides its own Unix-style shell & doesn't then >> depend on the conflict between the way command.exe & shell handle / >> and \ etc. I'm not sure if the others do. > > Probably not, although I tend to avoid pathing issues by changing to the > directory I want to use before I use the utilities. Having grep > available in a 'DOS' shell is extremely convenient. > I was thinking more along the lines of using \ to escape shell meta-characters and wondering whether command.exe might seek to interpret them as part of a path. -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk

On 17 Feb 2013 in soc.genealogy.computing, Ian Goddard wrote: > I was thinking more along the lines of using \ to escape shell > meta-characters and wondering whether command.exe might seek to > interpret them as part of a path. Ah. No, it doesn't. What gets me is that in the bash shell, text delimiters are single quotes; in cmd.com, they're double. I usually use bash, and when I try using single quotes in cmd.com, I get nothing. -- Joe Makowiec http://makowiec.org/ Email: http://makowiec.org/contact/?Joe Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/

On 17/02/2013 11:57, Ian Goddard wrote: > Joe Makowiec wrote: >> On 16 Feb 2013 in soc.genealogy.computing, Ian Goddard wrote: >> >>> Actually it was Cygwin http://www.cygwin.com/ I was thinking of. >>> It's a long time since I used it (much easier these days to just run >>> Linux) but IIRC it provides its own Unix-style shell & doesn't then >>> depend on the conflict between the way command.exe & shell handle / >>> and \ etc. I'm not sure if the others do. >> >> Probably not, although I tend to avoid pathing issues by changing to the >> directory I want to use before I use the utilities. Having grep >> available in a 'DOS' shell is extremely convenient. >> > > I was thinking more along the lines of using \ to escape shell > meta-characters and wondering whether command.exe might seek to > interpret them as part of a path. > You could try Grepwin http://tools.tortoisesvn.net/grepWin.html