[Top][All Lists]

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

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

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #62847] addpath fails to process some mapped network drives
Date: Thu, 4 Aug 2022 10:43:49 -0400 (EDT)

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

(couldn't resist to try, though I'm a bit swamped in work)

AFAICS, if the network subdir where opt_lbm.m lives is the active directory on
network drive letter Q, but not yet in the path:
when inside that subdir:
* canonicalize_file_name returns a UNC path if I feed it just the file name
'opt_lvm.m') as input
* if its input is 'Q:opt_lvm' (drive letter filename), it returns a path with
a drive letter (no UNC path)
* same if I feed it the full (non-UNC) path

 __wglob__  and 'dir' always return a non-UNC path

When that network subdir *IS* in the path, from that network subdir or
* which *always* returns a UNC path
* canonicalize_file_name and  __wglob__  return what I feed them, UNC path or
drive letter-path
It makes no difference whether there's a UNC or 'drive letter' path in the
subdir box in the file browser and main menu.

I hope I have described it adequately. There are myriads of options: in the
path or not, UNC or drive letter path in browser pane, in or outside pertinent
network subdir, network subdir active directory on the network drive or not,
... you name it. Plus I'm getting a bit hazy after a long day behind the


Reply to this item at:


Message sent via Savannah

reply via email to

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