[Octave-bug-tracker] [bug #49184] working directory logic seems sometimes distorted

[Hartmut]

URL:
  <http://savannah.gnu.org/bugs/?49184>

                 Summary: working directory logic seems sometimes distorted
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Sun 25 Sep 2016 11:17:02 PM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.0-rc2
        Operating System: Any

    _______________________________________________________

Details:

I have observed this with the current Octave 4.2.0-rc2 version under Linux
(self compiled on Ubuntu 14.04) as well as under Windows 7 (official exe
installer from alpha.gnu.org).

Here is how to reproduce the behavior under Linux:
* Generate the following m-file script in any folder of your home directory (I
gave it the name buggy_script.m):

cd "/opt/octave-4.2.0-rc2/scripts"
clear b
a = b

* Maybe change the folder name in the script to match your current
installation of Octave 4.2.0-rc2
* Load the script into the GUI editor
* Press the run button in the GUI editor, and click "yes" on the following "do
you want to change your working directory" button.
** result: "error: 'b' undefined near line 3 column 7"
* Press the run button AGAIN in the GUI editor.
** result: "error: 'buggy_script_linux' undefined near line 1 column 1"

At the end, the relevant script file IS in the current working directory.
Doing a simple "ls" command from the Octave CLI will show you it's there. But
you won't be able to run it any more from the GUI editor. You cannot even
start this script by typing its name into the Octave command line any more.

To this seems as if the logic of the current working directory gets distorted
by this. This is a regression, because it works fine under Octave 4.0.3.

The corresponding script to make this bug "work" under Windows is for
example:

cd "opt/octave-4.2.0-rc2/share/octave/4.2.0-rc2/m"
clear b
a = b






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49184>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/