[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 05:40:15 -0400 (EDT)

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

> If you browse that drive with the Windows Explorer, do the folders also end
with `$`?
* If I enter '\\<server>\company.local' in Windows Explorer's address bar
there is nothing shown. But that server address exists as there are no
* If I enter '\\<server>\company.local\full$' I see the contents of directory
'full$' (including 'path' (from 'full\path\to').
* If I enter '\\<server>\company.local\full' (w/o trailing '$') I get an error
"Windows cannot access ...".
* Now, if I enter 'Q:\' I see that root subdir 'full' (w/o trailing '$') is
actually a shortcut - apparently to '\\<server>\company.local\full$'. I cannot
verify the latter, but I suppose it has to be. And I have no idea where the
"physical" location of that shortcut is. Could be anywhere on the network.
Maybe it's even some sort of virtual thing.

So, there are also shortcuts in the mix. Do addpath / canonicalize_file_name
stumble over shortcuts? That would fit in nicely in the behavior I see.

BTW in a CMD window UNC paths aren't accepted on my virtual PC. The 'cd'
command there even says so: "CMD does not support UNC paths as current


Reply to this item at:


Message sent via Savannah

reply via email to

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