[Top][All Lists]

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

[Octave-bug-tracker] [bug #62847] addpath fails to process symlinks on m

From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #62847] addpath fails to process symlinks on mapped network drives
Date: Fri, 5 Aug 2022 13:09:00 -0400 (EDT)

Update of bug #62847 (project octave):

                  Status:               Need Info => Patch Reviewed         


Follow-up Comment #35:

Thanks for checking!

If I understand the POSIX documentation of `canonicalize_file_name` correctly,
a path containing a symbolic link (including to a UNC share) should be
returned with that symbolic link resolved. That means that the behavior of
`canonicalize_file_name` in Octave 7 is correct (bar the issue addressed in
this patch). It *should* return a UNC path in your case. The behavior in
previous versions of Octave was arguably incorrect.

IIUC, the paths that are stored in the load path are canonicalized. I don't
recall the exact reason for that.
But these two facts are probably why you are seeing those UNC paths in the
load path now.

Does something no longer work because of those UNC paths in the load path? Or
is it just for cosmetic reasons that you prefer the non-canonical path with
the mapped drive letter over the UNC path?
But you are right: This is probably a better topic for a new bug report. (A
first step would be to check why we are canonicalizing paths in the load path
currently. Maybe that is not necessary?)


Reply to this item at:


Message sent via Savannah

reply via email to

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