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

[Michael Godfrey]

Follow-up Comment #22, bug #42242 (project octave):

>From Mike's comment #20:

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?
============================================

This could be an important point. How does the interpreter
find that the file has been changed? Does it ever
leave the file open? Or, does it always fclose and
reopen the file?  It should not be necessary for the
editor to tell the interpreter it has changed the file
(I hate flags). But the interpreter may need a better
check, and if all else fails, a "changed_flag."

And, does the interpreter check mtime while the file
is open? This may not be NFS-safe either.


    _______________________________________________________

Reply to this item at:

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

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