Path: utzoo!attcan!uunet!wuarchive!emory!gatech!mcnc!gbyrd
From: gbyrd@mcnc.org (Gregory T. Byrd)
Newsgroups: comp.sys.ti.explorer
Subject: microExplorer timestamps and Zmacs
Summary: why is BOOT namespace in CST?
Keywords: microExplorer timezones Zmacs
Message-ID: <7261@alvin.mcnc.org>
Date: 31 Oct 90 19:55:42 GMT
Reply-To: gbyrd@mcnc.org (Gregory T. Byrd)
Followup-To: comp.sys.ti.explorer
Organization: Digital Equipment Corp. -- MCNC; RTP, NC
Lines: 58

Two questions:

1. Why does the BOOT site in the BOOT namespace believe that
   it is in timezone 6 (CST), regardless of what timezone
   I'm really in?  My namespace is set up for EST, the band was
   built in EST, time:*timezone* is bound to 5 (EST), 
   (time:print-current-time) prints the EST time, etc., etc. --
   BUT, the timestamps for files as shown by Dired are one
   hour later than they should be.  The MAC timestamps are
   correct -- e.g., the Mac thinks that a files was written
   at 12:23 (which it was), but Dired displays a timestamp
   of 13:23.  Presumably, it's converting 12:23 from CST
   to EST, but why?

   (I admit, this is only a minor annoyance, and I could
   solve it by pretending that I'm in the CST timezone, but
   I'm just too curious to let this go.)

2. This one is a major annoyance, although it too has a
   workaround.  (I thought it might be connected with #1,
   but now I don't think so.)

   Scenario:
   (a) I edit file FOO.LISP, which was last modified at 12:00
       (today, just to keep things simple).  It is now 12:30.
   (b) I modify the buffer and save it, using C-x C-s.
   (c) I modify the buffer again.
   (d) When I try C-x C-s again, I get the following warning:
        
           When you last read or wrote FOO.LISP
           it was FOO.LISP, created by [0,1] at 10/31/90 12:00:00,
           but now it is FOO.LISP, created by [0,1] at 10/31/90 12:10:00.
           Save it anyway? (Yes or No)

   (e) I answer YES and proceed.

   Zmacs seems to have forgotten the last time that I wrote the
   file, and thinks that someone else may have modified it while
   I had a copy in the buffer.  When I write it again, I get the
   same warning, but with the 12:10 timestamp replacing the 12:00
   one above.

   Workarounds:
   (a) Use C-x C-w.  (No warnings, presumably because it doesn't
       check the timestamp.)
   (b) Always revert the buffer after writing it -- Zmacs seems
       to remember the read time better that the last write time.

   Any ideas on how to fix this?  (I have Zmacs 6.5.)





-- 
...Greg Byrd             MCNC/Digital Equipment Corp.
   gbyrd@mcnc.org        P.O. Box 12889
   (919)248-1439         Research Triangle Park, NC  27709