From: fizzbintuesday@that-google-mail-domain.com   
      
   JJ wrote:   
   > On Thu, 17 May 2018 00:16:53 -0400, Tom Del Rosso wrote:   
   >> Apparently xcopy can't use exclude files with quotes.   
   >>   
   >> C:\TEMP>xcopy /exclude:"exclude 1.txt" test*.* d:   
   >> Can't read file: "exclude 1.txt"   
   >>   
   >> And I thought the API handled quotes so that every program would   
   >> treat quoted names the same way.   
   >   
   > The /EXCLUDE switch doesn't support long file name. The file path   
   > syntax which contains double quote characters.   
      
   It takes LFN but just not spaces.   
      
      
   > I'm guessing that Microsoft doesn't even bother to update it.   
   > It's still like that even in the latest Windows 10 build.   
      
   They don't bother to fix any bugs do they?  FC still has a 27 year old   
   bug that makes it report a file isn't found if its attributes are set.   
   The "Find-First" and "Find-Next" calls have the option of matching   
   attributes if a bit is set in a register.  They don't bother to change   
   1-bit in the object code.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)