[Octave-bug-tracker] [bug #62847] addpath incorrectly processes symlinks on mapped network drives

[Markus Mützel]

Update of bug #62847 (project octave):

                  Status:          Ready For Test => In Progress            

    _______________________________________________________

Follow-up Comment #48:

I was (erroneously) assuming that only network shares can be mapped to a drive
letter. But it looks like *any* directory on a share can be mapped to a drive
letter (e.g., `net use X: \\server\share\some\folder\on\the\share` will map
that *folder* as the entry point to the drive letter `X:`).

I'll try to have a look at it again with that in mind.

Given all those complications, I'm starting to doubt if treating mapped drives
differently in `canonicalize_file_name` was a good idea in the first place.
See: https://hg.savannah.gnu.org/hgweb/octave/rev/b47bf773c508

Maybe, we should just revert that change (and the follow-up changes) and leave
it at the UNC path that the Windows API functions return?


    _______________________________________________________

Reply to this item at:

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

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