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 13:10:10 +0100	[thread overview]
Message-ID: <87ee4tgz19.fsf@zoho.eu> (raw)
In-Reply-To: CAP_d_8U3E=FAQJ7XiNMnCi-Y4Gneo69KmEKVTuWWHOA7EVz7Gg@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

Yuri Khan wrote:

>> I keep seeing 88 for min-colors. I wonder if a different
>> number would be more appropriate, as it seems that 88 is
>> quite arbitrary.
>
> Historically, there existed terminals that supported
> a maximum of 8 colors, 16 colors, 88 colors (basic 16 +
> 4×4×4 color cube + 8 grays?), then 256 colors (basic 16 +
> 6×6×6 cube + 24 grays), and finally 24-bit color.

Were there no monochrome terminals?

My first computer was the Mac Plus:

  A compact Mac, the Plus has a 9-inch (23 cm) 512x342 pixel
  monochrome display with a resolution of 72 PPI, identical to
  that of previous Macintosh models. [1]

This didn't prevent it from having awesome graphics,
sometimes:

  https://dataswamp.org/~incal/pimgs/dc.png

1986 game!

You can run on Linux with the Mini vMac emulator [2] - mail me
if you need ROMs ...


[-- Attachment #2: dc.png --]
[-- Type: image/png, Size: 26930 bytes --]

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]


[1] https://en.wikipedia.org/wiki/Macintosh_Plus
[2] https://www.gryphel.com/c/minivmac/dnld_std.html

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

  parent reply	other threads:[~2022-01-27 12:10 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 [this message]
     [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
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=87ee4tgz19.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).