[Top][All Lists]

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

[Octave-bug-tracker] [bug #65069] Octave reports .m file undefined after

From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #65069] Octave reports .m file undefined after creating file on rclone share
Date: Thu, 21 Dec 2023 07:17:23 -0500 (EST)

Follow-up Comment #1, bug#65069 (group octave):

Octave uses folder timestamps to determine if a folder needs to be scanned for
potentially changed or new .m files.

Your description sounds like the file system on that rclone share doesn't
correctly update the folder timestamp when new files are added in that

You could probably work around that by re-initializing the search path after
you added a file on that share with the following command:


If the timestamps aren't updated when a new file is created, they potentially
aren't updated when a file is changed either. So, you might need to manually
trigger scanning for changed .m files whenever you change anything in a .m
file that Octave already ran before.

If the timestamps on that filesystem are indeed causing this behavior, another
workaround would be to move the files to a properly working (local?)
filesystem while you are making modifications to them.


Reply to this item at:


Message sent via Savannah

reply via email to

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