[Octave-bug-tracker] [bug #62847] addpath fails to process symlinks on mapped network drives

[Nicholas Jankowski]

Follow-up Comment #36, bug #62847 (project octave):

clarification to my comment #30:

the v7.2.0 canonicalized filename given in the first examples (just giving the
local filename rather than the "R:/..." and returning UNC paths starting with
\\) are the correct fully resolved UNC paths to the files.  The only problems
were the ones returned that starting with
"R:\PST_Storage_nicholas.jankowski...". (haven't been able to try the patch
yet)

the UNC paths returned do work for navigation, etc., within octave and windows
explorer. the only place they don't work is in the Windows Command Line, which
does work (out of the box) with UNC paths ("CMD does not support UNC paths as
current directories")[1]. It seems that it works from within Octave CLI, e.g.,
calling a cd or ls command. I only see the error if passing something to
system().  I do not know of any places within octave that might encounter this
specific problem (pkg?) mixing system commands with UNC paths, but that is the
only concern I can see with UNC path usage.

[1] https://devblogs.microsoft.com/oldnewthing/20070215-05/?p=28003


    _______________________________________________________

Reply to this item at:

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

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