octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #63996] Editor does not see equality of drive


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #63996] Editor does not see equality of drive letter paths and associated UNC path
Date: Tue, 4 Apr 2023 13:04:46 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?63996>

                 Summary: Editor does not see equality of drive letter paths
and associated UNC path
                   Group: GNU Octave
               Submitter: philipnienhuis
               Submitted: Tue 04 Apr 2023 07:04:44 PM CEST
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Microsoft Windows
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Tue 04 Apr 2023 07:04:44 PM CEST By: Philip Nienhuis <philipnienhuis>
At my company network I was editing and debugging an .m-file residing on a
network share. The subdir where that .m file lives is in the path, but that
mentions a UNC path rather than a drive letter.

When I wanted to add a breakpoint I got popups like the one shown in the
attached pic.
My conclusion is that the file editor (or is it 'file_in_load_path' or other
internal Octave functions behind the scenes?) doesn't recognize that the drive
letter path and the UNC path point to the very same file.

Quite intriguing is that I already had a few breakpoints in the file (I can
only have put them in by double-clicking in the left margin before running the
.m-file) and had execution stop at those breakpoints as well. So the popup
comes "as a surprise", right out of the blue.
I don't remember if I had saved the file in between runs before I got the
popup, but that may play a role.

Here I'll just mention the old bug reports bug #62847 and bug #62865 about
similar issues relating to drive letter / UNC paths and the search path. It
looks like the UNC vs drive letter saga in Windows networks keeps lingering on
... :-)







    _______________________________________________________
File Attachments:


-------------------------------------------------------
Date: Tue 04 Apr 2023 07:04:44 PM CEST  Name: UNCpath_vs_driveletter.png 
Size: 41KiB   By: philipnienhuis

<http://savannah.gnu.org/bugs/download.php?file_id=54560>

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63996>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

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