unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: paaguti@gmail.com, emacs-devel@gnu.org
Subject: Re: Question: How does color-lighten-name work?
Date: Fri, 28 Oct 2022 14:26:37 +0300	[thread overview]
Message-ID: <83h6zojij6.fsf@gnu.org> (raw)
In-Reply-To: <875yg4s71v.fsf@gmail.com> (message from Robert Pluim on Fri, 28 Oct 2022 10:09:48 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,  emacs-devel@gnu.org
> Date: Fri, 28 Oct 2022 10:09:48 +0200
> 
> >>>>> On Fri, 28 Oct 2022 10:09:34 +0300, Eli Zaretskii <eliz@gnu.org> said:
> 
>     >> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
>     >> Date: Fri, 28 Oct 2022 08:23:16 +0200
>     >> 
>     >> (require 'color)
>     >> (let ((newbg "#102030"))
>     >> (message "newbg: %s" newbg)
>     >> (setq newbg (color-lighten-name newbg 10))
>     >> (message "newbg: %s" newbg))
>     >> 
>     >> evaluated in the *scratch* buffer. will print the following:
>     >> 
>     >> newbg: #102030
>     >> newbg: #11ab23563501
>     >> 
>     >> Shouldn't the second colour spec have only 3 bytes?
> 
>     Eli> No, it uses the default format of 4 digits per component.
> 
>     Eli> We could perhaps add an additional optional argument to specify how
>     Eli> many digits per component to produce.
> 
> By the principle of least surprise, perhaps default to the same number
> of digits as the input?

That'd be a backwards-incompatible change.  Too late for that, I
think.  So if we introduce that, it will have to be via the additional
argument.  (FWIW, I see no surprise in the current behavior; I was
actually surprised that it was surprising.  You do understand that the
#RGB notations are equivalent no matter how many bits per component we
show, yes?)



  reply	other threads:[~2022-10-28 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28  6:23 Question: How does color-lighten-name work? Pedro Andres Aranda Gutierrez
2022-10-28  7:09 ` Eli Zaretskii
2022-10-28  8:09   ` Robert Pluim
2022-10-28 11:26     ` Eli Zaretskii [this message]
2022-10-28 14:46       ` Pedro Andres Aranda Gutierrez

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=83h6zojij6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=paaguti@gmail.com \
    --cc=rpluim@gmail.com \
    /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).