On Sun, Sep 8, 2013 at 1:11 PM, Thorsten Glaser <[email protected]> wrote: > Earnie Boyd dixit: > >>Is there a bugs database I can review? I've found an issue that you >>probably already know about. I just discovered this and have a small > > Actually, I do not have a Windows® system modern enough > to run the mksh/Win32 binary compiled by Michael, so, no > I don’t know about any problems other than those he told > me about. > > I *really* suggest you to contact the [email protected] > mailing list with things like this and also include Michael > directly with mksh/Win32-related issues (otherwise I’ll bounce > the messages into his general direction). > > If you agree, I’ll forward your original mail there? >
No, problem, please do; and this response. I contacted you since your address is on the web form as the creator. > > There’s a Launchpad bug tracker, but we (MirOS Project) > prefer a *lot* to use eMail (mailing lists) and IRC > instead. > >>fascination with the idea. The issue I discovered is with the display >>from echo of $PATH. Since the directory separator is still \ the > > I think the path separator must not be the backslash. > Well, maybe, maybe not. It Windows the directory separator is a \ and variables from the environment contain them. >>characters are being translated to the escaped special meaning. So >>\bin becomes <backspace>in and the result in reading it isn't pretty. > > Try using something like 「print -r -- "$PATH"」 instead. Yes, that does the job of issuing the string without translation of characters by escape sequence. There are however a lot of scripts using echo. It would probably work just fine if the mksh-win32 shell translated the \ to / in PATH during initialization but that might have side effects on some Windows processes. -- Earnie -- https://sites.google.com/site/earnieboyd
