[Top][All Lists]

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

[Octave-bug-tracker] [bug #62865] 'path' should return drive letter, not

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #62865] 'path' should return drive letter, not UNC path when 'addpath' was called with drive letter
Date: Thu, 11 Aug 2022 12:50:41 -0400 (EDT)

Follow-up Comment #6, bug #62865 (project octave):

Next issue:

At work, the GUI editor cannot add a network path to the load path through the
Not sure if this is a similar but separate bug from bug #82847, or something
While investigating I found a few other UNC path issues with a.o., the file
browser pane, I'll enter a separate report for that.

Let's see:

When I want to debug <some_function.m> that:
* is not in the path
* that was loaded in the editor through a drive letter path in the "Recent
Editor Files" drop-down list
* by clicking in the editor's left margin,
the editor yields a popup with the
"Change directory" / "Add directory to load path" / "Cancel" buttons.

Clicking the "Add directory to load path" button gets me an error message in
the command pane:

error: add_breakpoints_in_function: unable to find function <some_function>

Interestingly, the path shown in the popup is a "drive letter path", not a UNC

This does work (adding the subdir to the path through the popup) if I make use
of UNC paths (i.e., load the function through a UNC path entry in the Editor's
"Recent Editor Files" list.  In the popup the UNC path is shown in that case.

Note: CMD.EXE doesn't support UNC paths.


Reply to this item at:


Message sent via Savannah

reply via email to

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