From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?UTF-8?Q?Cl=C3=A9ment?= Pit-Claudel Newsgroups: gmane.emacs.bugs Subject: bug#25890: Default value of digits-per-component? Date: Wed, 29 Mar 2017 23:10:07 -0400 Message-ID: References: <6acea5ef-1c46-fefd-8cf6-290a0308185b@gmail.com> <83vaqr5w3e.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1490843475 13198 195.159.176.226 (30 Mar 2017 03:11:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 30 Mar 2017 03:11:15 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 Cc: 25890@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Mar 30 05:11:08 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ctQUO-0002J1-2z for geb-bug-gnu-emacs@m.gmane.org; Thu, 30 Mar 2017 05:11:08 +0200 Original-Received: from localhost ([::1]:33450 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ctQUQ-0000hC-Rs for geb-bug-gnu-emacs@m.gmane.org; Wed, 29 Mar 2017 23:11:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45158) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ctQUL-0000h7-BD for bug-gnu-emacs@gnu.org; Wed, 29 Mar 2017 23:11:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ctQUI-0003Vn-2V for bug-gnu-emacs@gnu.org; Wed, 29 Mar 2017 23:11:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:53598) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ctQUH-0003VY-VT for bug-gnu-emacs@gnu.org; Wed, 29 Mar 2017 23:11:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ctQUH-0000d0-Mf for bug-gnu-emacs@gnu.org; Wed, 29 Mar 2017 23:11:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 30 Mar 2017 03:11:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 25890 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 25890-submit@debbugs.gnu.org id=B25890.14908434152359 (code B ref 25890); Thu, 30 Mar 2017 03:11:01 +0000 Original-Received: (at 25890) by debbugs.gnu.org; 30 Mar 2017 03:10:15 +0000 Original-Received: from localhost ([127.0.0.1]:51796 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ctQTX-0000bz-9M for submit@debbugs.gnu.org; Wed, 29 Mar 2017 23:10:15 -0400 Original-Received: from mail-qk0-f170.google.com ([209.85.220.170]:36165) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ctQTV-0000bn-PJ for 25890@debbugs.gnu.org; Wed, 29 Mar 2017 23:10:14 -0400 Original-Received: by mail-qk0-f170.google.com with SMTP id p22so29534718qka.3 for <25890@debbugs.gnu.org>; Wed, 29 Mar 2017 20:10:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=QMoK8f85dpKY8itA5DYPb3m9SOfS7X9JjLXNSm9yp24=; b=PQ7EWqPkphgFLoYhKzih8En4O/2ldeiUy3wO7vkkw3NimuSxecenwGrDalESFlBEhO gab+I57F9shm1MOGU/w1IC4EntQL0c7T6ITtiyvWytrWsJmNMNu+XzCFg4P9dgJAPRZi Br2U3D3bpxUtfpM1pG0ifWiaGSAWXk4/jyaGKYAaVD/7ThHUnzVVxVt4vClGTrdqc5jE ShRJMXWl8XcGyuvN3GjqNdKLNpVuIRUT+eqxm0QI+omBvLC+PNwJqAtQzLYvftDdy9YL NPolc3VzVVs0e6YpVmH43eVx3lknhdOVh+WfY/shFb7dF+j4+Y1bF2iuv91LQSfCVun7 5JUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=QMoK8f85dpKY8itA5DYPb3m9SOfS7X9JjLXNSm9yp24=; b=ellMafV4LtMge2JjANxv6q99lXoBAsCghEGTIazVUYaZj7HrKH9PxdCaaY8os4Q+cW c+FYwnYI9rMdXzoDwwZJSWJy+RtvyhShfAi/aulANBN2sULxoOqArvFgDZIsQPY/4PJF gYTqtb31FxTAlFEI6EWvZsIfWSfGNQDBrLKVuFbZ1rtgLuLKu9YTseZy2Oqcue6q0XTH Th1TkC5MbAfs14J9RQ1Bxp3VM3I6TKdO76SR+3g9Ws0ca/B0svSA0T/GjWi4gjRoe5xk IrnpPb3eoMfp0WkIMVzsYfbo0wHgDDkjh5BbeH//03aZoFS3FSnSE2z+yEkB5SK5c1AK n6RQ== X-Gm-Message-State: AFeK/H2RWEze3NBDuRwBIsDpdiRZ4Oy1b6N6aqgKb3ELe8blJZgaM23NkegTeP54NLC7HA== X-Received: by 10.55.15.38 with SMTP id z38mr4426702qkg.114.1490843408390; Wed, 29 Mar 2017 20:10:08 -0700 (PDT) Original-Received: from [18.189.26.125] (dhcp-18-189-26-125.dyn.MIT.EDU. [18.189.26.125]) by smtp.gmail.com with ESMTPSA id r55sm607169qtr.16.2017.03.29.20.10.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 20:10:08 -0700 (PDT) In-Reply-To: <83vaqr5w3e.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:131080 Archived-At: On 2017-03-29 22:36, Eli Zaretskii wrote: >> Cc: Eli Zaretskii >> From: Clément Pit-Claudel >> Date: Wed, 29 Mar 2017 16:01:09 -0400 >> >>> If the change I made is nevertheless deemed too drastic, then what are >>> our alternatives? The only one I could think of is to define a new >>> function and deprecate color-name-to-rgb in favor of that new >>> function, which will then display warnings when code using it is >>> compiled, and eventually cause them to make changes in their code >>> anyway. Is that better? Or are there any better ideas? >> >> It sounds much better to me: the current solution breaks all code silently > > I'm not sure I understand how come all users of that function are > suddenly broken. A different result doesn't yet mean breakage, unless > the caller actually expected the precise format the old version was > producing, and relied on that. Is that indeed so in the callers you > saw? For me, yes, definitely: I was producing HTML webpages with inline CSS and LaTeX documents. Both of these got very confused when they started receiving a longer hex codes :) I don't know about the uses on GitHub. Clément.