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

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

[Octave-bug-tracker] [bug #56267] addpath() on Windows fails to recogniz


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #56267] addpath() on Windows fails to recognize same subdirs with different fileseps and case
Date: Sun, 5 May 2019 04:41:45 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

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

                 Summary: addpath() on Windows fails to recognize same subdirs
with different fileseps and case
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Sun 05 May 2019 10:41:43 AM CEST
                Category: Octave Function
                Severity: 2 - Minor
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

AFAIK addpath() normally recognizes if its argument is already in the PATH and
if so, doesn't add it to the PATH a second time.
But on Windows, where both '\' and '/' are accepted as file separators and
path-/filenames are case-insensitive, it gets confused by different fileseps
and different case in otherwise identical arguments, so the PATH can end up as
follows:

>> path

Octave's search path contains the following directories:

.
C:/Users/Philip/Desktop/getij/m-files
C:/Users/Philip/Desktop/Getij/m-files
C:\Users\philip\desktop\getij\m-files
C:\Programs\Octave\OCTAVE~1.0_2\mingw64\share\octave\packages\windows-1.3.1
:


Of course it's no big deal, Octave works fine anyway, but it is unneeded
cluttering of the search path.

Severity => Minor





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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