From: Barry OReilly <gundaetiapo@gmail.com>
To: bruce.korb@gmail.com, emacs-devel@gnu.org
Subject: How do I avoid purple-on-black and yellow-on-white?
Date: Sun, 2 Feb 2014 20:52:53 -0500 [thread overview]
Message-ID: <CAFM41H3UOOdkjUNq9R-fDfzM1CgmCx85j162yYxk0-M_o5A8AQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
Configuring Emacs to display white on black indeed seems
unpolished. When I started using Emacs, it took some experimentation
and web searching to arrive at:
* Customize frame-background-mode 'dark
* Customize inverse-video t (didn't observe this have any effect,
but it looked relevant)
* For graphical Emacs: run with -r flag
* For Emacs in terminal (also configured white on black): run with
-nw (no -r)
I didn't find a way to drop the -r flag in favor of pure Elisp config,
and still get good display.
I use graphical most of the time so don't generally notice terminal
display issues. Under this setup, the terminal colors are very
different from the graphical, but a brief look didn't uncover any poor
contrast.
In your case, the frame-background-mode variable makes the difference
between minibuffer-prompt face being medium blue or cyan, the latter
having better contrast on black. To confirm the value of that face, do
M-x customize-face RET minibuffer-prompt RET.
[-- Attachment #2: Type: text/html, Size: 1188 bytes --]
next reply other threads:[~2014-02-03 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 1:52 Barry OReilly [this message]
2014-02-04 0:21 ` How do I avoid purple-on-black and yellow-on-white? Trent W. Buck
2014-02-04 0:41 ` Bruce Korb
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=CAFM41H3UOOdkjUNq9R-fDfzM1CgmCx85j162yYxk0-M_o5A8AQ@mail.gmail.com \
--to=gundaetiapo@gmail.com \
--cc=bruce.korb@gmail.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 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.