[Octave-bug-tracker] [bug #42242] Octave does not always execute most recently saved file in an NFS directory

[Mike Miller]

Update of bug #42242 (project octave):

                Category:             Interpreter => GUI                    
              Item Group:                   Other => Incorrect Result       
                  Status:                 Invalid => Need Info              
             Open/Closed:                  Closed => Open                   

    _______________________________________________________

Follow-up Comment #20:

Just to summarize, this bug was closed because the NFS server time was out of
sync with the client machine's time and files had timestamps in the past when
they were saved. Octave relies on file mtime to be updated and correct
relative to host time.

Now the issue being raised is that Octave's built-in editor in the GUI saves
the file, but the interpreter runs an old copy because it does not see the
updated mtime. Since it is an integrated editor, and there is a "Save File and
Run" button, this should probably be fixed in some way. Reopening and
assigning to GUI.

So can this be fixed simply by trying to flush the file when saving from the
editor and before returning contol to the interpreter?

Or, since the editor *knows* that the file has been modified, should there be
a way for it to indicate that to the interpreter, to invalidate the
interpreter's state or last-read timestamp of the file?

    _______________________________________________________

Reply to this item at:

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

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