Giving up on colors, I need help

Giving up on colors, I need help

[William D. Colburn (Schlake)]

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 *);

Re: Giving up on colors, I need help

[Stefan Monnier]

> Back in 2007 I did (global-font-lock-mode 0), but that stopped working
> years ago.

emacs -Q --eval '(global-font-lock-mode 0)' ~/tmp/foo.el

shows the text in black-on-white with no funny colors, so if
(global-font-lock-mode 0) doesn't work for you, it must be because of
some other customization you have which triggers a bug (e.g. loading
a brain-dead package which thinks it's a good idea to call
(global-font-lock-mode 1)).

IOW, I recommend you M-x report-emacs-bug RET


        Stefan

Re: Giving up on colors, I need help

[Óscar Fuentes]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Back in 2007 I did (global-font-lock-mode 0), but that stopped working
>> years ago.
>
> emacs -Q --eval '(global-font-lock-mode 0)' ~/tmp/foo.el
>
> shows the text in black-on-white with no funny colors, so if
> (global-font-lock-mode 0) doesn't work for you, it must be because of
> some other customization you have which triggers a bug (e.g. loading
> a brain-dead package which thinks it's a good idea to call
> (global-font-lock-mode 1)).

I tried some of the methods described by the OP, and they work *after*
the file is visited, but starting with emacs -Q and evaluating this on
*scratch*:

(defun foo ()
  (message "hook")
  (global-font-lock-mode nil))

(add-hook 'c++-mode-hook 'foo)


then visiting a C++ file, the text is colorized. At that point,

M-x global-font-lock-mode

and the colors go away, but

M-x revert-buffer

colorizes the text again.

> IOW, I recommend you M-x report-emacs-bug RET

Yes, it is a glaring bug.

Re: Giving up on colors, I need help

[Stefan Monnier]

>   (global-font-lock-mode nil))

This turns global-font-lock-mode ON, so it's no wonder you see the text
colorized.  Try (global-font-lock-mode 0) or (global-font-lock-mode -1).
And don't bother putting it inside a hook, since it's global, just call
it once at top-level.


        Stefan

Re: Giving up on colors, I need help

[William D. Colburn (Schlake)]

On Fri, Feb 22, 2013 at 3:19 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>>   (global-font-lock-mode nil))
>
> This turns global-font-lock-mode ON, so it's no wonder you see the text
> colorized.  Try (global-font-lock-mode 0) or (global-font-lock-mode -1).
> And don't bother putting it inside a hook, since it's global, just call
> it once at top-level.

And years of pain I never understood suddenly comes to an end...


-- 
void *(*(*schlake(void *))[])(void *);