[Octave-bug-tracker] [bug #62865] 'path' should return drive letter, not UNC path when 'addpath' was called with drive letter

[Philip Nienhuis]

Follow-up Comment #4, bug #62865 (project octave):

What about this?


debug> help ismember

'\\<server>.cmpany.local\FULL$\path\to\some\subdir'

CMD.EXE was started with the above path as the current directory.

UNC paths are not supported.  Defaulting to Windows directory.

'ismember' is a function from the file
C:\Programs\Octave\Octave-8.0.0_20220807H\mingw64\share\octave\8.0.0\m\set\ismember.m


No idea if this can be harmful (not in this example, I got the help text). But
it makes me wonder what happens if one wants to invoke some function living in
a network drive in the path where the CMD processor is invoked behind the
scenes - unsure is that is a real-life viable scenario.

Whether the UNC path is the Real Thing or not, on Windows equivalent drive
letter paths seem to be more reliable in some cases.


    _______________________________________________________

Reply to this item at:

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

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