unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	 Jean Louis <bugs@gnu.support>,
	Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Need for colorful completing read
Date: Tue, 06 Sep 2022 17:38:14 +0000	[thread overview]
Message-ID: <87pmg8e73t.fsf@posteo.net> (raw)
In-Reply-To: <CAP_d_8UzEtMhk-uvOFqRfF1bhL_M9w0h8Gy6Ai5_c7ywuA+9NQ@mail.gmail.com> (Yuri Khan's message of "Tue, 6 Sep 2022 23:50:20 +0700")

Yuri Khan <yuri.v.khan@gmail.com> writes:

> On Tue, 6 Sept 2022 at 19:29, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
>> > So it looks like it.
>>
>> Then I guess we can use that in css-mode.
>
> Does anybody use X11 colors in web design though? I had an impression
> that most people™ define colors directly in #rrggbb or rgb(r, g, b) or
> rgba(r, g, b, a). Sometimes in hsl, especially if they want nice
> gradients. If they are wise enough, they define a few color-valued
> custom properties (css variables) at the root element level, and
> reference them from everywhere, but the color values are still mostly
> #rrggbb and determined by the brandbook rather than the X11 list.

FWIW I use them, though I don't create professional web sites.  That
being said, if css-mode offers completion it would still be nice to have
some kind of a idea what kind of colors some of the more outlandish
names represent.  There is also rainbow-mode, but that only works if the
text is already in the buffer.



  reply	other threads:[~2022-09-06 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 20:48 Need for colorful completing read Jean Louis
2022-09-05 20:51 ` Lars Ingebrigtsen
2022-09-05 21:07   ` Jean Louis
2022-09-06  4:11     ` Emanuel Berg
2022-09-06 10:02     ` Lars Ingebrigtsen
2022-09-06 10:20       ` Jean Louis
2022-09-06  5:06   ` Akib Azmain Turja
2022-09-06  8:59   ` Philip Kaludercic
2022-09-06 10:03     ` Lars Ingebrigtsen
2022-09-06 10:11       ` Philip Kaludercic
2022-09-06 10:27         ` Lars Ingebrigtsen
2022-09-06 16:50           ` Yuri Khan
2022-09-06 17:38             ` Philip Kaludercic [this message]
2022-09-06  5:05 ` Akib Azmain Turja
2022-09-11  6:26   ` Jean Louis

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=87pmg8e73t.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=larsi@gnus.org \
    --cc=yuri.v.khan@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.
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).