unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Yaseen Mowzer <yaseen@mowzer.co.za>
Cc: meta@public-inbox.org
Subject: Re: [PATCH v2] contrib/css/216light: increase contrast of normal text
Date: Mon, 17 May 2021 01:52:58 +0000	[thread overview]
Message-ID: <20210517015258.GA14414@dcvr> (raw)
In-Reply-To: <20210516084351.1157893-1-yaseen@mowzer.co.za>

Yaseen Mowzer <yaseen@mowzer.co.za> wrote:
> On my monitor #333 on #fff is a little bit hard to read. I think normal
> text should just be #000.

I wasn't completely sure about it, myself; but I can't stand
light backgrounds in general floaters in my eyes are getting
worse (AFAIK there's no treatment, either).

> The head style uses the contrast between #333 and #000 for emphasis. To
> preserve the emphasis `font-weight: bold` was added to the head style.
> ---
> 
> I changed my mind about the head style. I think we should make it bold
> instead of loosing the emphasis. This is more consitent with what git
> diff does.

OK, more inline...

> diff --git a/contrib/css/216light.css b/contrib/css/216light.css
> index c66cfdfe..c68ca9ce 100644
> --- a/contrib/css/216light.css
> +++ b/contrib/css/216light.css
> @@ -4,7 +4,7 @@
>   * Suitable for print, and blinding people with brightness.
>   * Haphazardly thrown together because bright colors hurt my eyes
>   */
> -* { background:#fff; color:#333 }
> +* { background:#fff; color:#000 }

I find #000 on #fff too intense for large swaths of text.
Would #030 or #003 (dark green/blue) work for you?

>  /*
>   * Underlined links add visual noise which make them hard-to-read.
> @@ -22,7 +22,7 @@ a:visited { color:#808 }
>   */
>  *.add { color:#060 }
>  *.del {color:#900 }
> -*.head { color:#000 }
> +*.head { color:#000; font-weight:bold }

I've been avoiding bold for stuff that might be important
because some fonts or low-res displays make bold hard-to-read.

Maybe something subtle like #300 work?  Or keep it #000
if foreground becomes #030 or #003.

(I think .head is the least important element to highlight by
 a long shot).

>  *.hunk { color:#960 }
>  
>  /*

  reply	other threads:[~2021-05-17  1:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16  8:20 [PATCH] contrib/css/216light: increase contrast of normal text Yaseen Mowzer
2021-05-16  8:43 ` [PATCH v2] " Yaseen Mowzer
2021-05-17  1:52   ` Eric Wong [this message]
2021-05-17  6:17     ` Yaseen Mowzer
2021-05-17  8:16       ` Eric Wong
2021-05-17 16:40         ` Yaseen Mowzer

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://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210517015258.GA14414@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=yaseen@mowzer.co.za \
    /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).