On Sat, Jul 19, 2014 at 3:18 PM, Eric Auer <e.a...@jpberlin.de> wrote:
>
> Hi Jeremy,
>
> > In shell/command.c the following patch should fix the issue (assuming
> > switchar changed).
> > @@ -331,8 +331,10 @@
> > break;
> > case CMD_SPECIAL_DIR: /* pass '\\' & '.' too */
> > if(*rest == '\\' || *rest == '.' || *rest == ':') break;
> > + if (!isoptch(*rest) && *rest == '/') break;
> > default: /* pass '/', ignore ',', ';' & '=' */
> > - if(!*rest || *rest == '/') break;
> > + if(!*rest || isoptch(*rest)) break;
> > if(isargdelim(*rest)) {
> > rest = ltrimcl(rest);
> > break;
>
> Strange idea, why would "/" always be a switchar
> even if you explititly configure switchar to be
> something else? Which Windows versions do that?
>
I'm not sure what you are asking. The default switchar is '/' and so will
be treated as an option specifier instead of directory unless the switchar
is changed.
> And of course: Which software is known to set the
> switchar to for example "-" while at the same time
> expecting "/" to be still simultaneously valid...?
>
> Regards, Eric
>
>
The first part is so / treated same as \ (but not if it is currently the
switch character, which by default it is).
The second part is so it does not hard code / as the switchar.
Note unless the switchar support is compiled in, then FreeCom hard codes it
to '/'. There may be a few other places in FreeCom that expect / as the
switchar; the only one I know of is the help text.
Jeremy
------------------------------------------------------------------------------
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
