octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #44814] which and run fail on windows for new


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #44814] which and run fail on windows for new files
Date: Sun, 12 Apr 2015 13:00:17 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Iceweasel/35.0.1

Update of bug #44814 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

Does this have to do with directory timestamps on your filesystem?

There was a similar bug about m-files in the root directory of a network drive
or a thumbdrive or something like that.

Octave expects the modification timestamp of the directory containing the
newly created m-file to be updated. Can you see what's going on with this
example?


>> format long
>> stat (pwd ()).mtime
## create new m-file
## verify new m-file exists and which fails
>> stat (pwd ()).mtime
## is there a way to force mtime update in windows? touch cmd?


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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