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

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

[Octave-bug-tracker] [bug #38823] Time stamp change opens search outside


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #38823] Time stamp change opens search outside build tree for "run-octave"
Date: Thu, 25 Apr 2013 00:05:13 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15

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

                 Summary: Time stamp change opens search outside build tree
for "run-octave"
                 Project: GNU Octave
            Submitted by: sebald
            Submitted on: Thu 25 Apr 2013 12:05:11 AM GMT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I am looking into the log z/color scale gnuplot problem using the "run-octave"
shell script file for running using the build tree.  I happened to have a
__gnuplot_get_var__.m file in the path that is described in my .octaverc file.
 When I launch Octave with /<fullpath>/run-octave the __gnuplot_get_var__.m
inside /<fullpath>/../octave/scripts/plot/private is used.  However, when I
make edits in /<fullpath>/../octave/scripts/plot/private/__go_draw_axes__.m
and save that file while Octave is still running, Octave then finds the
__gnuplot_get_var__.m in the search path described in my .octaverc file.  I
can tell because my __gnuplot_get_var__.m happens to be incompatible with the
current development version.

So, either:

1) A time stamp change on a file is causing Octave to disregard the conditions
set up in the "run-octave" shell script file.

or

2) Under "run-octave", Octave isn't initially finding a script file in the
path described in my .octaverc that it should be finding.

Not a high priority bug, and maybe it isn't even a bug if I'm overlooking
something.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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