Hi, On Fri, Jul 18, 2014 at 2:00 PM, Juan Manuel Guerrero <[email protected]> wrote: > > I do not know if this is the right place to report this FreCom issue
Dunno, not sure it's actively maintained by anyone anymore. http://www.freedos.org/software/?prog=command http://sourceforge.net/p/freedos/svn/HEAD/tree/freecom/ > I do not know if this issue is already well known but I would like to > report it anyway. > > If I use FreeCom 0.84-pre2 XMS_Swap [August 28 2006 00:32:15] shipped > with FreeDOS 1.1 and start the batch file in exactly the same way I get > the following output: > > As can be seen, FreCom seems to interpret any slash as an option marker > like in "/?" to get help. All microsoft command.com versions and also cmd.exe > do interpret the slash as an option marker only if it is preceded by some > kind of blank character. This makes it necessary to quote paths written in > unix-style like: > "../foo/bar/." > if they shall be passed as arguments to a batch file to be processed by > FreCom. > Is this behavior a bug or a feature? I definitely reported this same quirk to somebody a few years ago. Obviously it was never fixed. It was probably just an unintentional flaw or too obscure to worry about. I mean, most DOS programs don't use *nix slashes as path separators. I wish I had better news for you like, "I made a fix", but it's not really that easy. (Not impossible, just very annoying.) ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
