GNU bug report logs - #40863
[PATCH] Improve the display-time-world UI

Previous Next

Full log

Message #22 received at 40863 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 40863 <at> debbugs.gnu.org, stefan <at> marxist.se
Subject: Re: bug#40863: [PATCH] Improve the display-time-world UI
Date: Mon, 27 Apr 2020 15:00:37 -0400

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Noam Postavsky <npostavs <at> gmail.com>
>> Cc: Stefan Kangas <stefan <at> marxist.se>,  40863 <at> debbugs.gnu.org
>> Date: Mon, 27 Apr 2020 13:20:40 -0400
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> >> From: Stefan Kangas <stefan <at> 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.
>
> So you are saying that we should change these names from time to time
> just to make a point?

No, I think changing the name here makes it more readable (i.e., it's
not a random change, it's an improvement).  And I think this benefit
outweighs the possible existence of broken applications, or users
possibly preferring the current value (I will admit this weighting also
somewhat depends on the probability of these hypotheticals actually
turning out to be real, which I've no real basis for; you might judge
them to be more likely than I do).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.