From: "William D. Colburn (Schlake)" <schlake@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Giving up on colors, I need help
Date: Fri, 22 Feb 2013 11:27:42 -0700 [thread overview]
Message-ID: <CAL4MU-TOubMfpbHpmFsE61LD+t_SESq1YfMdtqhnr-+r4C8_Vg@mail.gmail.com> (raw)
Since October of 2007 I've fought an ever losing battle against emacs.
I want to be able to see the words on the screen. Either black words
on a white screen or white words on a black screen.
I'm finally defeated. My last stand had been, for the past few years,
to always type ESC-x text-mode every time I started emacs to make the
screen readable. But now, at my new job running 21.4.1 the colors
remain even in text mode.
Back in 2007 I did (global-font-lock-mode 0), but that stopped working
years ago. I added (defun turn-on-font-lock () "Turn off Font Lock
mode because it sucks." (global-font-lock-mode 0)) to keep it from
happened, but that doesn't do anything anymore. I tried (setq
font-lock-maximum-size -1) and (setq font-lock-maximum-size 0) and
(setq font-lock-maximum-size 1) but none of those helped. For my
frequently used mode I tried (add-hook 'python-mode-hook (lambda ()
(global-font-lock-mode nil))) and (add-hook 'python-mode-hook (lambda
() (font-lock-mode nil))) but that didn't work. I had been using
--color=no on the command line, which didn't really work either, and
which no longer exists.
And now that ESC-x text-mode doesn't work anymore I'm stumped. What
on earth do I have to do to turn off colors? Why is this so hard?
What am I missing?
--
void *(*(*schlake(void *))[])(void *);
next reply other threads:[~2013-02-22 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 18:27 William D. Colburn (Schlake) [this message]
2013-02-22 21:05 ` Giving up on colors, I need help Stefan Monnier
2013-02-22 22:07 ` Óscar Fuentes
2013-02-22 22:19 ` Stefan Monnier
2013-02-22 22:32 ` William D. Colburn (Schlake)
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=CAL4MU-TOubMfpbHpmFsE61LD+t_SESq1YfMdtqhnr-+r4C8_Vg@mail.gmail.com \
--to=schlake@gmail.com \
--cc=help-gnu-emacs@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.
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).