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: Impossible to customize world clock
Date: Tue, 09 Apr 2024 18:28:14 +0300	[thread overview]
Message-ID: <86edbewo6p.fsf@gnu.org> (raw)
In-Reply-To: <jwv7ch68tej.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier via Users list for the GNU Emacs text editor on Tue, 09 Apr 2024 11:12:42 -0400)

> Date: Tue, 09 Apr 2024 11:12:42 -0400
> From:  Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> 
> >> Hmm... it's too bad that in order to automatically make it work on both
> >> MS-Windows and other systems (by automatically choosing which var to
> >> use) we end up silently ignoring the user's config when the user isn't
> >> aware of this mechanism.
> >> 
> >> Maybe we should have chosen for `world-clock-list` a format like
> >> 
> >>     ("London" "Europe/London" "GMT0BST")
> >
> > I'm not sure it will work reliably, since the MS-Windows runtime
> > supports a very small number of zones via those legacy specifiers,
> > nowhere near the number of zones you will see in the zoneinfo
> > directory of a typical Posix host.
> 
> Oh, it wouldn't make any difference to what is supported and what is
> not: on MS-Windows we'd use the 3rd element of the lists, and on other
> systems we'd use the 2nd element of the list.  The purpose would be only
> to have a single variable, so the users are less likely to update one
> without knowing it's not the one they're using.

Then maybe I'm missing something because I don't understand how would
that help the OP.  He said:

> I add a new one (Europe/Berlin):
> 
>   '(zoneinfo-style-world-list
>     '(("America/Los_Angeles" "Seattle")
>       ("America/New_York" "New York")
>       ("Europe/London" "London")
>       ("Europe/Paris" "Paris")
>       ("Asia/Calcutta" "Bangalore")
>       ("Asia/Tokyo" "Tokyo")
>       ("Europe/Berlin" "Germany"))))

How would your suggestion help him to "add Europe/Berlin"?



  reply	other threads:[~2024-04-09 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 19:49 Impossible to customize world clock Kepa via Users list for the GNU Emacs text editor
2024-04-08 20:45 ` tpeplt
2024-04-09  4:00   ` Eli Zaretskii
2024-04-09 13:46     ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-04-09 14:32       ` Eli Zaretskii
2024-04-09 15:12         ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-04-09 15:28           ` Eli Zaretskii [this message]
2024-04-09 16:52             ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-04-09 18:34               ` Eli Zaretskii
2024-04-09 18:41                 ` Emanuel Berg
2024-04-10  2:32                   ` Eli Zaretskii
2024-04-10  2:48                 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-04-10 13:53                   ` Eli Zaretskii
2024-04-09 13:52     ` tpeplt
2024-04-09  2:36 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2024-04-13 12:15 Kepa via Users list for the GNU Emacs text editor

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=86edbewo6p.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).