unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: min-colors 88
Date: Thu, 27 Jan 2022 19:42:51 +0100	[thread overview]
Message-ID: <87a6fhf2ac.fsf@zoho.eu> (raw)
In-Reply-To: MuRiba1--3-2@tutanota.com

fatiparty--- via Users list for the GNU Emacs text editor wrote:

> I could be mistaking the interpretation of the hex-codes to
> the number of colours available.

Notation: #RRGGBB

Each channel: 1 byte = 8 bits

e.g., say "winter blue" is #385d7d, that is binary

  111000 1011101 1111101

As you see, there are

  (16^2)^3 = 16 777 216

colors available!

(or computed from the 24-bit binary,

  2^24 = the same)

However, in _another_ sense there are (or can be) just 8
colors available, and 8 bright versions of them! Here are, for
example, mine! I have them in a tailored file so they are easy
to see and edit, they are then processed to the less-palatable
original Linux format, and the colors appear in the
ttys/Linux VTs/the console.

So the file:

   normal                         bright
   bk  r   g   y  bl   m   c   w  bk    r   g   y  bl   m   c   w
r  0 255   0 190 100 180   0 150  115 255   0 255 125 250  90 210
g  0  50 155 190 100 105 180 150  115  80 185 127 125  90 255 180
b  0  50   0   0 255   0 180 150  115  80   0   0 255 250 255 140

See, there are 8 colors! ........ OK, 16 then!

But you also see that each channel is 0-255. So then we are
back at

  256^3 = 16 777 216

colors available!

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2022-01-27 18:42 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  6:14 min-colors 88 fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27  6:33 ` Yuri Khan
2022-01-27 11:48   ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 12:10   ` Emanuel Berg via Users list for the GNU Emacs text editor
     [not found] ` <CAP_d_8U3E=FAQJ7XiNMnCi-Y4Gneo69KmEKVTuWWHOA7EVz7Gg@mail.gmail.com-MuPEX1J--7-2>
2022-01-27  6:39   ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27  6:46 ` Eli Zaretskii
2022-01-27  8:43   ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27  9:56     ` Eli Zaretskii
2022-01-27 10:44       ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 10:54         ` Bastian Beranek
2022-01-27 11:01         ` Eli Zaretskii
2022-01-27 11:43           ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 11:49             ` Eli Zaretskii
2022-01-27 12:27               ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 12:59             ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 11:47           ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 11:50             ` Eli Zaretskii
2022-01-27 13:00               ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 13:03               ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 13:33                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 15:14                 ` Eli Zaretskii
2022-01-27 18:09                   ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 18:30                     ` Eli Zaretskii
2022-01-27 18:43                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 18:46                       ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 19:46                         ` Eli Zaretskii
2022-01-27 18:47                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-28  7:58                         ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28  8:07                           ` Eli Zaretskii
2022-01-28  8:59                             ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 11:36                               ` Eli Zaretskii
2022-01-28 11:54                                 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 12:16                                   ` Eli Zaretskii
2022-01-28 12:55                                     ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 13:19                                       ` Eli Zaretskii
     [not found]                                     ` <MuVkMCN--3-2@tutanota.com-MuVxLzA----2>
2022-01-28 13:55                                       ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 21:27                                         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-28 12:53                                 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 13:17                                   ` Eli Zaretskii
2022-01-28 13:49                                     ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 14:34                                       ` Eli Zaretskii
2022-01-28 15:12                                         ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 16:56                                           ` Eli Zaretskii
2022-01-28 21:21                           ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 18:42                     ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2022-01-27 11:59           ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 11:50   ` Emanuel Berg via Users list for the GNU Emacs text editor

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=87a6fhf2ac.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).