unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Elijah G <eg642616@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Questions about submiting a package to ELPA
Date: Wed, 17 Apr 2024 15:38:48 +0300	[thread overview]
Message-ID: <86v84ggo4n.fsf@gnu.org> (raw)
In-Reply-To: <CACnP4NJ-V3-OqL6qizmEJG2TuYdLPhAnDffdUXtNysk-N5sM7g@mail.gmail.com> (message from Elijah G on Tue, 16 Apr 2024 21:11:14 -0600)

> From: Elijah G <eg642616@gmail.com>
> Date: Tue, 16 Apr 2024 21:11:14 -0600
> Cc: emacs-devel@gnu.org
> 
> On Tue, Apr 16, 2024 at 8:30 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > Adding colors is meaningless, because colors are defined by the
> > underlying platforms.  You can add faces, using defface, where the
> > colors is defined by their hex RGB values.
> > If this doesn't answer your questions, please tell more details:
> > why do you want to add these
> > colors and how you intend to use them.
> 
> When I was adding support for colorizing HTML colors names into my
> package I found that emacs already provides some of them,
> so I thought it would be a good idea to use those colors already provided.
> However some of these colors are in lowercase and most HTML color
> names uses Capital Case and/or PascalCase, i think that maybe
> add their Pascal or Capital case would help to packages that uses HTML
> colors such as my package, rainbow-mode and maybe the colorize feature from
> css-mode; this is because users must lowercase the color name for
> preview/colorize
> them.
> But i think i must not use `defined-colors' for this behavior and
> define the colors
> myself.

What you describe seems to talk about faces, not colors.  Colors in
Emacs are not first-class citizens, they are attributes of faces.  So
I still don't understand why you cannot define faces for your package,
and define the colors for those faces via hex RGB values, as we do
when no existing color is exactly like we want.



      reply	other threads:[~2024-04-17 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 19:17 Questions about submiting a package to ELPA Elijah G
2024-04-17  2:30 ` Eli Zaretskii
2024-04-17  3:11   ` Elijah G
2024-04-17 12:38     ` 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

  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=86v84ggo4n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eg642616@gmail.com \
    --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 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).