On Tue, Sep 10, 2013 at 6:05 PM, Michael Langguth wrote:
> i saw this issue too. for a moment i thought about translating PATH to
> forward slashes. most other windows programs work with both type of slashes
> but not all. thus, i decided to leave it as ist is.
>
> for now, as thorsten mentioned, "print -r" does the trick. if you prefer
> forward slashes in PATH you can place this command at the beginning of your
> scripts:
>
> PATH=${PATH//\\/\/}One can use either method as long as a method doesn't give unexpected results to the end user. If you translate PATH to / then you need to translate it back to \ before spawning a process because Windows OS will not do the right thing with / in PATH. I would suggest training echo to not translate the escaped characters of an environment variable. My interest in mksh-w32 is one of a replacement for MSYS. Getting rid of the man-in-the-middle runtime would help speed up operations and the less work the binary does spawning the better. At some point in the distant future I'll take a look at the code and try to help out. In the meantime I'll be trying to see what coreutils I can get to compile without any extra libraries (and yes I know about gnuWin32 project). -- Earnie -- https://sites.google.com/site/earnieboyd
