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

[Philip Nienhuis]

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

Yep it's pretty mysterious.

Reading up on bug #62576 + the Stackoverflow posting mentioned there I get
more and more confused about the UNC paths versus drive letter issue.
I can follow your rationale for making the chance that I backed out locally.
Makes me wonder when Octave started to morph drive letter paths into UNC
paths, and most of all, why it is specifically 'addpath' that doesn't work
anymore with drive letters. 'which' and 'cd' seem to have no issue with it.

Anyway, as I wrote I can work around it for the time being.
I suggest to lower priority (but leave Item Group "regression").

I hope (but maybe in vain) that after the summer I'll have more free time to
spend on Octave.  Even then I see no way I can debug this, if only for the
sheer size of the unstripped Octave "installer" or "dist archive". There's no
way I can transfer files that large to my virtual work PC, not even in
chunks.



    _______________________________________________________

Reply to this item at:

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

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