all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Church <chrchr@gmail.com>
Cc: 70963-done@debbugs.gnu.org
Subject: bug#70963: [PATCH] Add Oklab color space utility functions in color.el.
Date: Sun, 19 May 2024 11:25:25 +0300	[thread overview]
Message-ID: <86jzjqb43u.fsf@gnu.org> (raw)
In-Reply-To: <CAKUFMvfHHvbBJGTnRDexRPd4Q-M6CU7SkCWwm3mci4QJ4=RwZw@mail.gmail.com> (message from Robert Church on Wed, 15 May 2024 09:58:27 -0700)

> From: Robert Church <chrchr@gmail.com>
> Date: Wed, 15 May 2024 09:58:27 -0700
> 
> This patch adds functions to convert to and from the Oklab perceptual color space to color.el. Oklab
> preserves the perceived brightness ot a color as the hue and saturation change. It is especially useful for
> programmatically generating color schemes, and can be used directly in CSS in current web browsers.
> 
> Oklab is described here: https://bottosson.github.io/posts/oklab/

Thanks, I installed this on the master branch.

For the future, please try to observe our conventions for patch
submissions:

  . accompany the patches with suitable ChangeLog-style commit log
    messages (you can see the examples in what I actually committed,
    and the instructions are in CONTRIBUTE)
  . leave 2 spaces between sentences in doc strings and comments
  . announce any worthy changes in NEWS and propose changes for the
    manuals when appropriate

I'm closing the bug report with this message.





      parent reply	other threads:[~2024-05-19  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 16:58 bug#70963: [PATCH] Add Oklab color space utility functions in color.el Robert Church
2024-05-15 18:00 ` Andrea Corallo
2024-05-15 18:41   ` Robert Church
2024-05-18 22:16     ` Stefan Kangas
2024-05-19  8:25       ` Eli Zaretskii
2024-05-15 18:00 ` Eli Zaretskii
2024-05-19  8:25 ` Eli Zaretskii [this message]

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=86jzjqb43u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70963-done@debbugs.gnu.org \
    --cc=chrchr@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 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.