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//\\/\/}

--lan

Reply via email to