[Octave-bug-tracker] [bug #29878] Octave does not detect new script files when using external drive

[Judd Storrs]

Follow-up Comment #11, bug #29878 (project octave):

> I don't see how this is relevant, I was referring to script files, not data
files.

Ultimately I think it's the modification times stored in the file system that
matter. I was using save because I don't know if touch exists on windows.

Do you have any explanation why it would be different for an external FAT
drive relative to an internal FAT drive? Are you certain your internal drives
are not NTFS?

The stat()'s indicate that time stamping should be working with the exception
that perhaps octave's time resolution is wrong for this drive. All the mtimes
are even numbers (even when the ctime is odd and even after an odd delay)
which may indicate that the limit should be two seconds for FAT on Windows.
Often it looks like the ctime has been rounded up to the next even number.

Are you able to compile octave? I suspect changing time_resolution in
liboctave/file-stat.h to 2.0 seconds instead of 1.0 seconds may solve the
problem.

    _______________________________________________________

Reply to this item at:

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

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