|
From: | Nicholas Jankowski |
Subject: | [Octave-bug-tracker] [bug #62576] dir() behavior changed in octave 7.1.0 for network drives |
Date: | Mon, 20 Jun 2022 11:00:19 -0400 (EDT) |
Follow-up Comment #12, bug #62576 (project octave): just noting that in some older versions of either Octave or Windows (I can't remember specifically which) CMD cannot handle UNC paths. This used to be a problem in Octave and I had mapped certain network shares to drive letters to get around this. The expectation was that once something was mapped to a drive letter one would no longer see the UNC path under any typical usage. issue highlighted here (but not really explaining which versions it's relevant in): https://stackoverflow.com/questions/45071585/cmd-does-not-support-unc-paths-as-current-directories _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?62576> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |