From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] Make display-time-mode time zone configurable
Date: Thu, 3 Mar 2016 16:24:57 -0800 [thread overview]
Message-ID: <56D8D5D9.1020007@cs.ucla.edu> (raw)
In-Reply-To: <20160303003904.GA6892@holos>
On 03/02/2016 04:39 PM, Mark Oteiza wrote:
>
>> I'm afraid we're starting to go in circles. I'm curious about why one
>> would want to change just the mode-line's time zone, and you're
>> responding that it's because one would want to change just the
>> mode-line's time zone. :-)
> You are repeatedly responding to the use case with the non-solution of
> setting the time zone globally in Emacs.
Yes, we are indeed going around in circles. The problem is that I
haven't seen a real use case yet.
We already have a solution for an expert who for some reason needs a
mode line in a different time zone from the Emacs default. As I
understand it, you're asking to complicate Emacs by adding a feature to
make it easier to configure Emacs to have this unusual behavior, so that
a non-expert can more easily arrange for Emacs mode lines to be in the
"wrong" time zone. My problem is that I don't understand why a
non-expert would want to do that. And without understanding the actual
need, it's hard to see why the proposed feature's benefits would be
worth its costs.
next prev parent reply other threads:[~2016-03-04 0:24 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
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 [this message]
-- 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=56D8D5D9.1020007@cs.ucla.edu \
--to=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 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).