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

[John W. Eaton]

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

"i'm pretty sure the underlying problem predates the gui"

I guess you could see the same problem if you used the edit function or if you
used fopen/fprintf/fclose to generate a .m file on the fly.  The timestamp of
the file is probably updated with sufficient resolution for us to notice the
change in most cases.  But if I recall correctly, the load path code won't
notice if writing a file doesn't also trigger a change in the timestamp of the
containing directory.  That's because it will assume that nothing in the
directory has changed and then will skip looking for new or modified files
inside those directories.  If that is the problem, then we can avoid it by
changing the load-path code so that we can mark files (or directories)
individually as "modified" when we know that changes have been made.

If that's not sufficient (maybe an external editor writes a file in one of
these directories for which the timestamp is not properly updated) then maybe
we could try to detect which directories have this bad property and flag them
for special treatment?  But I'm not sure how to do that without having write
permission to the directory.

Or is there some other efficient solution that I'm not seeing?


    _______________________________________________________

Reply to this item at:

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

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