[Octave-bug-tracker] [bug #64363] [octave forge] (io) xlswrite to existing file fails if temp dir is on different drive

[Philip Nienhuis]

Follow-up Comment #5, bug #64363 (project octave):

The error seen in the 3rd verbatim block of comment #1 seems to be due to an
issue with the 'make_absolute_filename' function. That is conspicuous in the
first lines there but I overlooked it:

>> cd c:
>> xlswrite ("z:subst2.xlsx", {"Col1", "Col2"; 5, 6; 7, 8}, "", "", "oct")
xlsclose: could not zip files in C:\Users\philip\AppData\Local\Temp\oct-IOmPy1
to c:\\z:subst2.xlsx
:


Setting a breakpoint in xlsclose.m at L.139
( xls = __OCT_spsh_close__ (xls, "xlsclose", force); )
and doing this:

debug> xls
xls =
  scalar structure containing the fields:
    xtype = OCT
    app = xlsx
    filename = Z:bug64363B.xlsx
:

debug> make_absolute_filename (xls.filename)
ans = c:\Z:bug64363B.xlsx

shows that make_absolute_filename cannot process / is oblivious to the working
directory on another drive.
ISTR this issue has been reported, or at least noted, several years ago in the
course of other issues pertaining to 'make_absolute_filename' and/or
'canonicalize_file_name' functions and how these work on Windows. But maybe
here it's due to the subst command.

However this is not the bug the OP posted.
I'll check if I can reproduce that some other way.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64363>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/