Hi, On Sat, Jul 19, 2014 at 12:00 AM, Mateusz Viste <mate...@viste.fr> wrote: > > I think this problem goes beyond "path separators". As I understand it, any > argument including a slash character > will get exploded. So yes, this might be used as path separator, but not > only. For eg. sed expects slash > delimited values inside a single argument.
sed can use other delimiters, if slash is too prohibitive. Sometimes that makes things easier to read and write. Just for silly example (tested under Cygwin): echo $PATH | sed -e '/.*\(\/cygdrive\/c\/rugxulo\/watcom19\/BINNT\).*/s//\1/' ... vs. ... echo $PATH | sed -e '\,.*\(/cygdrive/c/rugxulo/watcom19/BINNT\).*,s,,\1,' Oops. Or did you mean that this bug in FreeCOM might break sed invocations? I doubt it, the double quotes after -e probably protect it from munging. > @Juan - you also write about other "different issues and limitations" - could > you please post us a list? > Even if FreeCom is semi-maintained nowadays, it would still be interesting to > know what kind of quirks you found there.. The only one I'm aware of is the "read from NUL" bug, which Jeremy already fixed in his unofficial Git snapshots. (Yes, for some reason, DJGPP insists on reading from that, heh.) http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp-workers/2014/03/28/16:38:35 ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
