Le 2013-09-05 12:36, Jim Henderson a écrit :
> On Thu, 05 Sep 2013 09:35:45 -0400, Francois Labreque wrote:
>
>> If you remember, a few months ago, I was ranting about a very expensive
>> commercial network monitoring software suite that specifically mentioned
>> NOT using spaces in directory names for exactly that reason.
>>
>> Unfortunately the Windows port of that software suite is installed under
>> C:\Program files, so they require that the disk have short file names
>> enabled, so that they can use C:\PROGRA~1 instead.
>
> I don't see how that's an OS issue, though.
>

Never said it was an os issue.

> How's the shell supposed to know if you mean a space in a filename or a
> space between parameters unless you tell it which you mean?
>

100% Agreed.  It's Patrick who was complaining that CMD.EXE still had 
problems with that and I simply said that *nix shells weren't any better.



-- 
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/*    flabreque    */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/*        @        */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/*   gmail.com     */}camera{orthographic location<6,1.25,-6>look_at a }

Post a reply to this message