[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #49203] File visible in File Browser, but inte

From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #49203] File visible in File Browser, but interpreter can't see it right away when on network drive
Date: Mon, 31 Oct 2016 19:59:15 +0000 (UTC)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0

Follow-up Comment #14, bug #49203 (project octave):

huh... I was expecting 1:28pm to match the mtime report.

A bit of googling does seem to indicate that this could just be a Windows
quirk. There doesn't seem to be a standard for NTFS on what should and
shouldn't cause a date modified update to a folder (new file, changed file
contents, should it always just match newest file in folder, etc.)

I assume the answer is yes, but can a Linux user chime in on whether there is
an equivalent specification that is more clear? 

If the issue is that Octave wouldn't be able to rely on date-modified to know
whether to check for new functions, I'm not sure what other approach would be
practical, especially if it's a some-Windows unique problem and
Octave-on-Windows developers are few and far in between. 

Other than 'Matlab doesn't have this problem'... so it must use some other
method not vulnerable to this issue. 

Bradley, have you tried the 'rehash' command?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]