unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Protesilaos Stavrou <info@protesilaos.com>
To: Arthur Miller <arthur.miller@live.com>
Cc: emacs-devel@gnu.org
Subject: Re: solarized
Date: Wed, 16 Sep 2020 21:07:21 +0300	[thread overview]
Message-ID: <87ft7hvbmu.fsf@protesilaos.com> (raw)

Arthur Miller <arthur.miller@live.com> [2020-09-16, 15:38 +0200]:

> Protesilaos Stavrou <info@protesilaos.com> writes:
>> On another note, do we really need to strictly conform with the
>> 16-colour palette?

> Batsov's Solarized gives you total of 32 colors. I certainly don't want to see
> all 32 colors at once in the gui :-). Anyway 16 of those are ment for
> extreme cases, and are just shades of eight accented colors, ligher and darker.

Agreed!  I never advocated for adding rainbows anywhere.  My point is
that the "extreme cases" that need more refined colouration are not that
uncommon after all.  And I gave specific examples, such as diffs with
word-wise changes (and Magit), isearch, occur, completion UIs.

> If those are not enough for some extreme case, user can always do what
> they do now, specify rgb value directly; but for *most* part, hopefully
> 16 colors would be enough. Nobody said it has to be enough for
> *everybody everywhere*.

That is always an option.  My impression, however, is that we are
thinking about how to improve upon the state of affairs.  One such way
is to offer more complete face/colour coverage for everyone (and they
can still configure it afterwards).  To that I also add the
accessibility angle.  Perhaps I misunderstood the intent of this
discussion, so please accept my apologies.

>> In my experience, 16 colours is too limited of a set to design bespoke,
>> usable, and pleasing interfaces that match the wide array of needs an
>> Emacs user has.
> Design literature on contrary says something in lines of "less is more",
> both when it comes to color and form.
>
> Too many colors and you get rainbow. Look at dired+ screenshot I
> attached. Every "property" is coded in different color, and it just
> looks horrible when put together.
>
> Another subject, similar to gui theme colors, is syntax highlighting. Too much
> syntax highlighting can be as detrimental as none, see for example this paper:
>
> https://pdfs.semanticscholar.org/d14b/edf3f58080ecf7a92f60746371b894a7bc08.pdf
>
> and this screenshot:
>
> https://imgur.com/zhCs4Bv
>
> Maybe some thoughts here:
>
> https://www.linusakesson.net/programming/syntaxhighlighting/

These are all interesting and fecund.  A good design must avoid
exaggerations, rainbow effects, and design for its own sake.

This, however, is an indictment against poorly implemented themes,
though not extended colour palettes as such.  Your attached screenshot
uses what looks like ~14 colours.

-- 
Protesilaos Stavrou
protesilaos.com



             reply	other threads:[~2020-09-16 18:07 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 18:07 Protesilaos Stavrou [this message]
2020-09-17 14:55 ` solarized Arthur Miller
2020-09-17 15:27 ` solarized Arthur Miller
  -- strict thread matches above, loose matches on Subject: below --
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 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                   ` solarized Arthur Miller
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

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=87ft7hvbmu.fsf@protesilaos.com \
    --to=info@protesilaos.com \
    --cc=arthur.miller@live.com \
    --cc=emacs-devel@gnu.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.
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).