[Octave-bug-tracker] [bug #53539] GUI file browser date stamps / editor script file appear modified when parsing date strings

[Ian McCallion]

Follow-up Comment #18, bug #53539 (project octave):

I too have been having problems with using the TZ environment variable. The
script below demonstrates one of the problems I found that may relate to this
bug. It shows an unwanted interaction between using TZ for the purposes of the
application and Octave's probably inappropriate dependency on the current
value of of TZ in monitoring the path for changed files. (Caveat. I'm on
windows)

Before launching this script, create a valid do-nothing function called
dummy.m. An empty file does not show the problem

---------
% Before launching this script, create a valid do-nothing function called
dummy.m. an empty file does not show the problem
system('touch dummy.m') % make sure timestamp is NOW
setenv('TZ', 'UTC0'); % !!!!! USE A TIMEZONE THAT IS WESTERLY FOR YOUR
LOCATION !!!!
mktime(localtime(1)); % This is necessary only in Octave for Windows to bypass
a bug in the posix layer which will be reported separately
pause (2); % Does not always happen without the pause

% the next command should report that the file has a timestamp in the future
dummy
setenv('TZ', '')
mktime(localtime(1));
-----------

    _______________________________________________________

Reply to this item at:

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

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