[Octave-bug-tracker] [bug #60122] Save and Run in editor does not always save

[John W. Eaton]

Follow-up Comment #34, bug #60122 (project octave):

"the new data was written to disk and accessible by other programs. Octave
just didn't think it had to look for the change."

Maybe we need a way for the GUI to signal that a file has been written.  Then
the interpreter can respond to that signal by  doing whatever is needed to
tell the load path and/or function table that the function corresponding to
the file should be considered out of date so that it will be parsed again. 
Then Octave will not have to rely on directory timestamps being updated
correctly.



    _______________________________________________________

Reply to this item at:

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

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