[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #62865] 'path' should return drive letter, not

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #62865] 'path' should return drive letter, not UNC path when 'addpath' was called with drive letter
Date: Tue, 9 Aug 2022 14:37:16 -0400 (EDT)

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

What about this?

debug> help ismember


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

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:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]