[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #62847] addpath fails to process network pathn
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames |
Date: |
Tue, 2 Aug 2022 11:44:18 -0400 (EDT) |
Follow-up Comment #12, bug #62847 (project octave):
I've tried a hopefully more systematic approach (found some time in between
assignments). It looks inconsistent with parts that I wrote in comment #7,
notably behavior of the subdir boxes in the file browser and main menu. That
*seems* to always work, also with UNC paths.
##========================================================================
## with pertinent network subdir IN the path:
>> cd ('Q:\full\path\to')
## Works fine. Note: no '$' after 'full' entered. With it it won't work
## from within pertinent subdir on network where opt_lvm.m lives
>> which opt_lvm
'opt_lvm' is a function from the file
'\\<server>.company.local\full$\path\to\opt_lvm.m'
## Note '$' appearing after first subdir on server (or is it already a share)
>> canonicalize_file_name ('opt_lvm')
ans = '\\<server>.company.local\full$\path\to\opt_lvm.m'
## Note '$' appearing after first subdir on server (or is it a share)
## Elsewhere on that network drive, or on local drive
>> which opt_lvm
'opt_lvm' is a function from the file
'\\<server>.company.local\full$\path\to\opt_lvm.m'
## Note '$' appearing after first subdir on server (or is it a share)
>> canonicalize_file_name ('opt_lvm')
ans =
## (empty)
## Copying Q:\full\path\to into box in main menu or browser pane + <Enter>
## ==> Works fine, is accepted
##==============================================================================
## With pertinent subdir NOT in path
>> cd ('Q:\full\path\to')
## Works fine
## from within pertinent subdir
>> which opt_lvm
'opt_lvm' is a function from the file
'\\<server>.company.local\full$\path\to\opt_lvm.m'
## Note '$' appearing after first subdir on server (or is it already a share)
>> canonicalize_file_name ('opt_lvm')
ans = '\\<server>.company.local\full$\path\to\opt_lvm.m'
## Note '$' appearing after first subdir on server (or is it a share)
## But now look here:
>> canonicalize_file_name ('Q:opt_lvm')
ans = 'Q:\full\path\to\opt_lvm.m'
## Note drive letter rather than UNC
## Elsewhere on that network drive, or on local drive
>> which opt_lvm
## empty
>> canonicalize_file_name ('opt_lvm')
ans =
## (empty)
## Copying Q:\full\path\to into box in main menu or browser pane + <Enter>
## ==> Works fine, is accepted
## ==========================================================
Funnily, starting in the network subdir holding 'opt_lvm.m', then going to E:
(entering 'E:\' in the box), then:
>> canonicalize_file_name ('T:opt_lvm.m')
ans = Q:\full\path\to\opt_lvm.m
Then, in file browser back to the network subdir, and pressing the 'one subdir
level up' button, I get
>> canonicalize_file_name ('T:opt_lvm.m')
ans =
## empty
The '$' character that shows up in UNC paths may be a red herring, I think
it's merely the literal "low-level" name of the share.
Again, simply strrep'ing 'Q:' by '\\<server>.company.local' in
'Q:\full\path\to' makes it all work.
So, as far is I can see it's just addpath() that doesn't work with the network
drive letters on my work system.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62847>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, (continued)
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Philip Nienhuis, 2022/08/01
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Philip Nienhuis, 2022/08/01
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Philip Nienhuis, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Philip Nienhuis, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Philip Nienhuis, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames,
Philip Nienhuis <=
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Philip Nienhuis, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Philip Nienhuis, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Philip Nienhuis, 2022/08/02
- [Octave-bug-tracker] [bug #62847] addpath fails to process network pathnames, Markus Mützel, 2022/08/03
- [Octave-bug-tracker] [bug #62847] addpath fails to process some mapped network drives, Markus Mützel, 2022/08/03
- [Octave-bug-tracker] [bug #62847] addpath fails to process some mapped network drives, Markus Mützel, 2022/08/03
- [Octave-bug-tracker] [bug #62847] addpath fails to process some mapped network drives, Philip Nienhuis, 2022/08/03