unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: "W. Greenhouse" <wgreenhouse@riseup.net>
Cc: Mark Oteiza <mvoteiza@udel.edu>, emacs-devel@gnu.org
Subject: Re: [PATCH] Make display-time-mode time zone configurable
Date: Tue, 16 Feb 2016 09:11:12 -0800	[thread overview]
Message-ID: <56C35830.4080107@cs.ucla.edu> (raw)
In-Reply-To: <87ziv0lo6i.fsf@example.com>

On 02/16/2016 06:33 AM, W. Greenhouse wrote:
> Also, as far as parts of Emacs that deal with time zones, there's also 
> `calendar-time-zone', which uses a totally different format (offset in 
> minutes, instead of zoneinfo-style names)! The calendar also seems to 
> NIH the handling of daylight saving time.

Yes, the calendar code predates the new support for time zones at the 
lower level, and it suffers because of that. For example, if you had 
started Emacs in Cancun last year at 2015-02-01 01:59, its calendar 
would have been messed up, because Cancun changed its clocks a minute 
later (a time zone change, not a daylight-saving change) and Emacs would 
have cached the wrong standard time zone. Eventually we should fix this 
sort of bug by having the calendar code use the new lower-level 
primitives better....

> Now that I understand the role of `display-time-string-forms', I can 
> fix the problem for myself there without Mark's proposed defcustom, 
> but the defcustom raises visibility a lot for others who might have 
> the same desired wall-clock configuration as I. 

OK, how about if we wait for others to have problems that cannot be 
solved via display-time-string-forms and deal with the issues that come 
up then.



  reply	other threads:[~2016-02-16 17:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 22:02 [PATCH] Make display-time-mode time zone configurable Mark Oteiza
2016-02-16  4:45 ` Paul Eggert
2016-02-16 14:33   ` W. Greenhouse
2016-02-16 17:11     ` Paul Eggert [this message]
2016-02-19  2:32       ` Mark Oteiza
2016-02-19  2:37   ` Mark Oteiza
2016-02-19  4:57     ` Paul Eggert
2016-02-19 17:14       ` Mark Oteiza
2016-02-19 18:02         ` Paul Eggert
2016-02-22  0:45           ` Mark Oteiza
2016-02-22  5:27             ` Paul Eggert
2016-03-03  0:39               ` Mark Oteiza
2016-03-04  0:24                 ` Paul Eggert
  -- strict thread matches above, loose matches on Subject: below --
2016-03-04 22:25 Mark Oteiza
2016-03-05  1:35 ` Paul Eggert

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=56C35830.4080107@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=mvoteiza@udel.edu \
    --cc=wgreenhouse@riseup.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).