[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25890: `color-values` gives wrong value
From: |
Eli Zaretskii |
Subject: |
bug#25890: `color-values` gives wrong value |
Date: |
Fri, 10 Mar 2017 15:32:58 +0200 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: "mail\@yo.eki.do" <mail@yo.eki.do>, 25890@debbugs.gnu.org
> Date: Fri, 10 Mar 2017 12:07:18 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I'm open to alternative ideas for how to solve the original bug in a
> > less intrusive way. I just don't think defaulting to 2 would be such
> > an alternative, because the underlying issues are very subtle, and if
> > we continue using 2 as the default, users of that function will never
> > discover that they need to use 4. But maybe there are other ways that
> > leave everyone more happy.
>
> The normal way to introduce incompatible changes like this is to
> introduce a new function and mark the old function as obsolete, isn't
> it? (Then remove the old function in about ten years time. :-))
I asked about that in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25525#68,
but no one answered. The disadvantage would be that those packages
need to change their code anyway, now or in "ten years time". If
that's deemed a better way, I can do it.
- bug#25890: `color-values` gives wrong value, (continued)
bug#25890: `color-values` gives wrong value, address@hidden, 2017/03/10
bug#25890: `color-values` gives wrong value, Eli Zaretskii, 2017/03/10
bug#25890: `color-values` gives wrong value, Lars Ingebrigtsen, 2017/03/10
bug#25890: `color-values` gives wrong value,
Eli Zaretskii <=
bug#25890: `color-values` gives wrong value, address@hidden, 2017/03/11