From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Adding some convenience functions to color.el
Date: Fri, 9 Jun 2023 10:26:57 +0300 [thread overview]
Message-ID: <CAJddU=oK8tvS8BK_7w-iugGxUwdJN_PMw=Hvj0jEeNjkm2mctg@mail.gmail.com> (raw)
In-Reply-To: <83v8fx15wq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
> From: Eli Zaretskii <eliz@gnu.org>
> We already have color-dark-p (and color-name-to-rgb to complement it),
> so I'm not sure I understand the rationale for these functions. Can
> you explain more why you needed them?
Sorry I totally missed color-dark-p. I did not check faces.el and
color-dark-p was in faces.el.
Having color-name-to-hsl is just a convenience function to make it easier
when working in some
color spaces. Because some operations are easier in certain color spaces.
On Fri, Jun 9, 2023 at 9:55 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
> > Date: Fri, 9 Jun 2023 02:57:41 +0300
> >
> > Today I was messing around with some theme that made use of color.el
> and I noticed some functions
> > that might be of use could be added to color.el to help with the
> conditionally assigning setting some
> > colors based on lightness or darkness of some other color. I wondered if
> it might be useful to other
> > users and if it might be worth adding it to color.el. I
>
> We already have color-dark-p (and color-name-to-rgb to complement it),
> so I'm not sure I understand the rationale for these functions. Can
> you explain more why you needed them?
>
[-- Attachment #2: Type: text/html, Size: 2095 bytes --]
next prev parent reply other threads:[~2023-06-09 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 23:57 Adding some convenience functions to color.el Yilkal Argaw
2023-06-09 6:22 ` Philip Kaludercic
2023-06-09 6:55 ` Eli Zaretskii
2023-06-09 7:26 ` Yilkal Argaw [this message]
2023-06-09 7:34 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJddU=oK8tvS8BK_7w-iugGxUwdJN_PMw=Hvj0jEeNjkm2mctg@mail.gmail.com' \
--to=yilkalargawworkneh@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.