unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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 10:11:33 +0000	[thread overview]
Message-ID: <87y1uwg6cq.fsf@posteo.net> (raw)
In-Reply-To: <87a67cx1ir.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 06 Sep 2022 12:03:56 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Would there be any way to re-use this when completing color-names in CSS?
>
> I haven't looked at the CSS code -- are CSS colours the same as the "OS
> colours"?

According to https://en.wikipedia.org/wiki/Web_colors:

          The first versions of Mosaic and Netscape Navigator used the
          X11 color names as the basis for their color lists, as both
          started as X Window System applications

          [...]

          Several colors are defined by web browsers. A particular
          browser may not recognize all of these colors, but as of 2005,
          all modern, general-use, graphical browsers support the full
          list of colors. Many of these colors are from the list of X11
          color names distributed with the X Window System.

So it looks like it.



  reply	other threads:[~2022-09-06 10:11 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 [this message]
2022-09-06 10:27         ` Lars Ingebrigtsen
2022-09-06 16:50           ` Yuri Khan
2022-09-06 17:38             ` Philip Kaludercic
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=87y1uwg6cq.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=larsi@gnus.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. 
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).