🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.ti.explorer
3 messages
3 total messages Started by Gregory T. Byrd Wed, 31 Oct 1990 19:55
microExplorer timestamps and Zmacs
#267
Author: Gregory T. Byrd
Date: Wed, 31 Oct 1990 19:55
58 lines
2760 bytes
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
microExplorer timestamps and Zmacs
#269
Author: David A. Moon
Date: Wed, 31 Oct 1990 21:18
9 lines
758 bytes
    Date: Wed, 31 Oct 1990 14:55 EST
    From: gbyrd@mcnc.org  (Gregory T. Byrd)

    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?

Texas chauvinism, that's all.
Re: microExplorer timestamps and Zmacs
#270
Author: Jamie Zawinski
Date: Wed, 31 Oct 1990 22:52
19 lines
1507 bytes
In article <7261@alvin.mcnc.org> gbyrd@mcnc.org (Gregory T. Byrd) wrote:
> 
> 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. --

Is the timezone field in the namespace set to a number (5) or a string
("EST")?  The Explorer time code is somewhat confused w.r.t.  daylight savings
time.  If the namespace contains a string, like "EDT" or "EST", sometimes an
extra hour will be subtracted, because it is trying to compensate for DST
twice (this is from memory, so might not be totally accurate).  Anyway, I had
this problem and made it go away by changing the string to a number.

Of course, the real solution is to lobby your politicians to do away with
daylight savings time entirely.  Daylight Savings Time - Just Say No.

		-- Jamie
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads