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

[Markus Mützel]

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

I *think* I'm able to reproduce the issue with this information now.
On the server side within a shared folder:

mklink /D test_C \\Markus-PC\C$


Additionally, I had to execute this on the client side or the symlink couldn't
be followed:

fsutil behavior set symlinkevaluation R2R:1


When I map the share on the client to Z:, the following happens with
`canonicalize_file_name` in Octave:

canonicalize_file_name ('Z:\test_C\Octave')
ans = Z:\Octave


The first part of the path got "eaten". Maybe that is what is causing the
issues for you...

I'd guess the correct behavior according to the POSIX documentation would be
for this to return `\\Markus-PC\C$\Octave`.


    _______________________________________________________

Reply to this item at:

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

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