unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Richard Stallman <rms@gnu.org>
Cc: Tim Cross <theophilusx@gmail.com>, emacs-devel@gnu.org
Subject: Re: solarized
Date: Fri, 18 Sep 2020 08:43:52 +0200	[thread overview]
Message-ID: <VI1PR06MB45266E0DC046EF5AE7483CF7963F0@VI1PR06MB4526.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <E1kJ7mE-0003Gl-0P@fencepost.gnu.org> (Richard Stallman's message of "Fri, 18 Sep 2020 00:13:38 -0400")

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > While I think these discussions are very valuable, I just wanted to
>   > mention one aspect of the Solarized theme which I think is quite
>   > important. It is one of the few themes with a defined underlying
>   > philosophy/principal. Many other themes are just something someone has
>   > defined, felt it looked good and released it. Solarized has a more
>   > formal definition.
>
> I understand that.  I'm proposing to do something similar except
> eliminating the goal of light-dark inversion symmetry.

Regardless of the colors choice; what I find useful is the logical
separation of color in two sorts: base colors and accent colors. Accents
are ment to be used for things that has to stand out, like a window
number on modeline, or a reserved word in a programming language. Base
colors are those used as bg/fg and other basic things that many packages
in Emacs don't need to touch. For that reason I think Solarized approach
is good for a framework choice.

If 8+8 is enough or not, I don't know. Maybe Batsov's approach is good
about a variation of accents colors, 8 lighter + 8 darker which can be
calculated by elisp automatically, or maybe some other division is better?

For the color choice, it is personal preference; I am sure different
cultures can manage color choices for themselves; i.e; make the
framework provide mechanism not policy.

For the concrete proposal, maybe it is best to start by providing a
framework of logical placeholders as well worded by Dmitry (I think) as
a first step; once there is a framework let then speak about some color
functions and elisp to automate calculation of choice, inversions etc.



  parent reply	other threads:[~2020-09-18  6:43 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  3:48 solarized Richard Stallman
2020-09-15  8:29 ` solarized Protesilaos Stavrou
2020-09-15  9:14   ` solarized Yuri Khan
2020-09-15 10:16     ` solarized Protesilaos Stavrou
2020-09-15 13:39       ` solarized Theodor Thornhill
2020-09-15 14:05         ` solarized Gerry Agbobada
2020-09-15 14:40           ` Theme generator (was: solarized) Stefan Monnier
2020-09-15 16:26             ` Theme generator Arthur Miller
2020-09-15 20:14               ` Stefan Monnier
2020-09-15 20:35                 ` Stefan Monnier
2020-09-15 20:44                   ` Arthur Miller
2020-09-16  1:49             ` Theme generator (was: solarized) Tim Cross
2020-09-17  0:25               ` chad
2020-09-17 14:25                 ` Theme generator Arthur Miller
2020-09-16  5:03             ` Theme generator (was: solarized) Richard Stallman
2020-09-15 20:28         ` solarized Protesilaos Stavrou
2020-09-15 20:50           ` solarized Praharsh Suryadevara
2020-09-16  5:05       ` solarized Richard Stallman
2020-09-16  8:27         ` solarized Protesilaos Stavrou
2020-09-16 13:38           ` solarized Arthur Miller
2020-09-17  3:57           ` solarized Richard Stallman
2020-09-17  7:53             ` solarized Gian Uberto Lauri
2020-09-17 15:56               ` solarized Drew Adams
2020-09-18  4:08               ` solarized Richard Stallman
2020-09-18  4:08               ` solarized Richard Stallman
2020-09-18 16:44                 ` solarized Drew Adams
2020-09-17 14:11             ` solarized Arthur Miller
2020-09-17 23:39               ` solarized Tim Cross
2020-09-18  4:13                 ` solarized Richard Stallman
2020-09-18  5:49                   ` solarized Tim Cross
2020-09-18  6:43                   ` Arthur Miller [this message]
2020-09-16 13:06         ` solarized Arthur Miller
2020-09-17  3:53           ` solarized Richard Stallman
2020-09-15 11:26   ` solarized Göktuğ Kayaalp
2020-09-15 12:15     ` solarized Elias Mårtenson
2020-09-15 12:56       ` solarized Göktuğ Kayaalp
2020-09-16  1:30         ` solarized Tim Cross
2020-09-16 10:21           ` solarized Göktuğ Kayaalp
2020-09-16 12:53             ` solarized Arthur Miller
2020-09-16 22:09             ` solarized Tim Cross
2020-09-17 14:29               ` solarized Arthur Miller
2020-09-18 13:32               ` solarized Stefan Kangas
2020-09-18 15:53                 ` solarized Arthur Miller
2020-09-18 16:03                 ` solarized Arthur Miller
2020-09-19  4:00                 ` solarized Richard Stallman
2020-09-20 20:18                   ` solarized Bozhidar Batsov
2020-09-15 12:05   ` WCAG AAA and Emacs themes Dmitry Gutov
2020-09-15 20:22     ` Protesilaos Stavrou
  -- strict thread matches above, loose matches on Subject: below --
2020-09-16 18:07 solarized Protesilaos Stavrou
2020-09-17 14:55 ` solarized Arthur Miller
2020-09-17 15:27 ` solarized Arthur Miller

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=VI1PR06MB45266E0DC046EF5AE7483CF7963F0@VI1PR06MB4526.eurprd06.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=theophilusx@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.
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).