From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40863@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#40863: [PATCH] Improve the display-time-world UI
Date: Mon, 27 Apr 2020 13:20:40 -0400 [thread overview]
Message-ID: <85y2qg976f.fsf@gmail.com> (raw)
In-Reply-To: <831roa731a.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 26 Apr 2020 17:08:33 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Kangas <stefan@marxist.se>
>> Date: Sun, 26 Apr 2020 10:56:03 +0200
>>
>> -(defcustom display-time-world-buffer-name "*wclock*"
>> +(defcustom display-time-world-buffer-name "*World Clock*"
>
> Is this part really necessary? what if some application or user out
> there expects the old name?
If an application expects a particular name, then it's already broken
because the user can change the defcustom at any time, right? And if a
user expects the old name, they can customize it back to the old value.
next prev parent reply other threads:[~2020-04-27 17:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 8:56 bug#40863: [PATCH] Improve the display-time-world UI Stefan Kangas
2020-04-26 14:08 ` Eli Zaretskii
2020-04-26 14:19 ` Stefan Kangas
2020-04-27 17:20 ` Noam Postavsky [this message]
2020-04-27 18:31 ` Eli Zaretskii
2020-04-27 19:00 ` Noam Postavsky
2020-04-27 19:35 ` Eli Zaretskii
2020-04-27 22:00 ` Dmitry Gutov
2020-04-27 23:04 ` Noam Postavsky
2020-05-01 15:03 ` Stefan Kangas
2020-05-01 15:13 ` Eli Zaretskii
2020-05-01 16:26 ` Stefan Kangas
2020-05-01 17:57 ` Eli Zaretskii
2020-05-01 18:07 ` Dmitry Gutov
2020-05-01 18:18 ` Eli Zaretskii
2020-04-27 22:58 ` Basil L. Contovounesios
2020-05-02 11:50 ` Stefan Kangas
2020-05-23 13:44 ` Basil L. Contovounesios
2020-05-02 16:10 ` Stefan Kangas
2020-05-02 18:00 ` Stefan Kangas
2020-05-23 13:43 ` Basil L. Contovounesios
2020-08-07 17:23 ` Stefan Kangas
2020-08-07 17:51 ` Basil L. Contovounesios
2020-08-09 22:11 ` Stefan Kangas
2020-08-18 13:49 ` Lars Ingebrigtsen
2020-08-18 14:37 ` Stefan Kangas
2020-08-18 18:23 ` Stefan Kangas
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=85y2qg976f.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=40863@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).