From: Mark Oteiza <mvoteiza@udel.edu>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Make display-time-mode time zone configurable
Date: Thu, 18 Feb 2016 21:37:23 -0500 [thread overview]
Message-ID: <20160219023723.GB15748@holos> (raw)
In-Reply-To: <56C2A950.3080102@cs.ucla.edu>
On 15/02/16 at 08:45pm, Paul Eggert wrote:
> Mark Oteiza wrote:
> > +(defcustom display-time-zone nil
> > + "Variable specifying the time zone used in `display-time-string-forms'.
> > +See the function `format-time-string' for an explanation of
> > +its ZONE variable."
> > + :type '(choice (const :tag "Emacs Local Time" nil)
> > + (const :tag "Universal Time" t)
> > + (const :tag "System Wall Clock Time" wall)
> > + (string "Time Zone Rule"))
> > + :link '(function-link format-time-string)
> > + :group 'display-time)
>
> This new defcustom seems to duplicate some or all of the existing defcustom
> time-stamp-time-zone. Should there be just custom var? or if there should be
> two, how should they differ in operation?
I suppose ideally there would just be one; however, it appears to me
that lots of time-related things are fragmented across Emacs. For
instance, setting 24hr clock in display-time has its own defcustom, but
to do the same for things that use calendarfu involves setting
calendar-time-display-form.
This patch just conveniently exposes the ZONE feature in
display-time-mode in the same way time-stamp-time-zone does in
time-stamp.el. Would it make sense to put a defcustom in (I guess)
time.el and have time-stamp.el use it?
next prev parent reply other threads:[~2016-02-19 2:37 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
2016-02-19 2:32 ` Mark Oteiza
2016-02-19 2:37 ` Mark Oteiza [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160219023723.GB15748@holos \
--to=mvoteiza@udel.edu \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.