From: Bruce Korb <bruce.korb@gmail.com>
To: "Trent W. Buck" <trentbuck@gmail.com>
Cc: emacs development <emacs-devel@gnu.org>
Subject: Re: How do I avoid purple-on-black and yellow-on-white?
Date: Mon, 3 Feb 2014 16:41:44 -0800 [thread overview]
Message-ID: <CAKRnqNL_HhHcdup_rFqg9f4nsRf8rUezS_fEEs_WHbOeD10YAg@mail.gmail.com> (raw)
In-Reply-To: <87r47jybg2.fsf@gmail.com>
I guess I am just lazy. I don't care about setting weirdo terminal modes.
I am not interested in a full palate of subtle color differences.
Black and white worked just fine. Having several contrasting colors
is very nice so I can see a clear distinction between comments and
regular code. That is all very nice indeed. But when you start having
dozens of colors, the contrast between some of the colors is not
going to be very great. But there should be a few fundamental
rules that emacs obeys:
1. if the background is white, do not use yellow for anything
2. if the background is dark, do not use purple or dark blue for anything.
If you want a subtle color difference between normal comments and
Doxygenated comments, fine. It is just simply that the contrast
between any characters and their background *MUST NOT BE SUBTLE*
and I should not be required to go do hours of research to figure out
how to fiddle settings so that it doesn't happen. I bumped into
dark purple on black and the result could not be read (without highlighting
the text, and even then it was not easy.)
Thank you. Regards, Bruce
next prev parent reply other threads:[~2014-02-04 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 1:52 How do I avoid purple-on-black and yellow-on-white? Barry OReilly
2014-02-04 0:21 ` Trent W. Buck
2014-02-04 0:41 ` Bruce Korb [this message]
2014-02-04 3:26 ` Stefan Monnier
2014-02-07 19:54 ` Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2014-02-04 2:53 Barry OReilly
2014-02-02 21:36 Bruce Korb
2014-02-02 23:47 ` Trent W. Buck
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKRnqNL_HhHcdup_rFqg9f4nsRf8rUezS_fEEs_WHbOeD10YAg@mail.gmail.com \
--to=bruce.korb@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=trentbuck@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.