unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Timezone change in US
Date: Tue, 13 Mar 2007 23:12:49 +0200	[thread overview]
Message-ID: <uhcsoq23y.fsf@gnu.org> (raw)
In-Reply-To: <m3tzwprswg.fsf@lugabout.jhcloos.org> (message from James Cloos on Tue, 13 Mar 2007 12:48:24 -0400)

> From: James Cloos <cloos@jhcloos.com>
> Copyright: Copyright 2007 James Cloos
> Date: Tue, 13 Mar 2007 12:48:24 -0400
> Cc: help-gnu-emacs@gnu.org
> 
> 
> Probably a stupid question, but what happens if you set your TZ
> variable to just 'EST5EDT'?  Or 'EST5EDT4,M3.2.0/2:00,M11.1.0/2:00'?
> 
> 02:00 is the default for the time string, so this should be the same
> as what you had:  'EST5EDT4,M3.2.0,M11.1.0'.  Does that work?
> 
> The 4 after EDT is also superfluous.  So each of these may be worth
> a try:
> 
> EST5EDT,M3.2.0/2,M11.1.0/2
> EST5EDT,M3.2.0/2:00,M11.1.0/2:00
> EST5EDT,M3.2.0,M11.1.0

I don't think Windows time routines support the above syntax.
See:

   http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/HTML/_crt__tzset.asp

Maybe the problem is precisely that tcsh sets TZ to this form, which
confuses Emacs on Windows.  In that case, running Emacs from without
tcsh should solve the problem.

> I just tried your TZ setting on my linux box, and it did the right
> thing (matching the output of TZ=US/Eastern or TZ=America/New_York
> with a current zoneinfo database).

Note that this Posix syntax of TZ, and the zoneinfo database, are also
not supported by the Windows time routines.

> So this is a win32 or mingw32 specific bug.

Perhaps it is a w32 specific bug, but then why does it work for me?

  reply	other threads:[~2007-03-13 21:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 15:31 Timezone change in US Chris McMahan
2007-03-12 16:58 ` Maarten Bergvelt
2007-03-12 17:01   ` Chris McMahan
2007-03-12 21:58 ` Eli Zaretskii
     [not found] ` <mailman.851.1173736718.7795.help-gnu-emacs@gnu.org>
2007-03-13 13:28   ` Chris McMahan
2007-03-13 16:48     ` James Cloos
2007-03-13 21:12       ` Eli Zaretskii [this message]
2007-03-14 11:42         ` James Cloos
2007-03-14 18:52           ` Eli Zaretskii
     [not found]         ` <mailman.916.1173872744.7795.help-gnu-emacs@gnu.org>
2007-03-14 12:49           ` Chris McMahan
2007-03-14 13:22             ` Chris McMahan
2007-03-14 19:02               ` Eli Zaretskii
     [not found]               ` <mailman.936.1173898991.7795.help-gnu-emacs@gnu.org>
2007-03-15 14:37                 ` Chris McMahan
2007-03-15 20:10                   ` Eli Zaretskii
     [not found]                   ` <mailman.971.1173989456.7795.help-gnu-emacs@gnu.org>
2007-03-16 12:25                     ` Chris McMahan
2007-03-16 13:11                       ` Eli Zaretskii
2007-03-16 13:58                       ` Stefan Monnier
2007-03-14 18:58             ` Eli Zaretskii
2007-03-13 21:05     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uhcsoq23y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).