[Octave-bug-tracker] [bug #47609] zip.m: errrors when zipping to a directory with spaces in name on Windows

[Mike Miller]

Follow-up Comment #2, bug #47609 (project octave):

Is the *.* wildcard expected to match directory names with no extension in
Windows typically? That seems like a more generic problem/misunderstanding not
specific to zip.

I got some errors due to paths with spaces in Debian with 4.0.1, but not with
the default branch:


>> out = zip ("dir_no_spaces/foo1.zip", "file*", "dir_no_spaces");
out = 
{
  [1,1] = file1
  [1,2] = file2
  [1,3] = file3
}
>> out = zip ("dir_no_spaces/foo2.zip", "dir_no_spaces/file*");
out = 
{
  [1,1] = dir_no_spaces/file1
  [1,2] = dir_no_spaces/file2
  [1,3] = dir_no_spaces/file3
}
>> out = zip ("dir with spaces/foo3.zip", "file*", "dir with spaces");
out = 
{
  [1,1] = file1
  [1,2] = file2
  [1,3] = file3
}
>> out = zip ("dir with spaces/foo4.zip", "dir with spaces/file*");
out = 
{
  [1,1] = dir with spaces/file1
  [1,2] = dir with spaces/file2
  [1,3] = dir with spaces/file3
}


So no errors due to spaces here, and no errors due to spaces in Philip's
examples either, just errors due to backslash file separator.

That's suspicious that the same path results in no error in the previous
example. How is that working? What is cmd in the case where it does work and
why does that work and not the other?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47609>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/