unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: karl@freefriends.org (Karl Berry)
Cc: emacs-devel@gnu.org
Subject: Re: can't turn off font-lock
Date: Tue, 14 Aug 2007 06:26:25 +0300	[thread overview]
Message-ID: <uy7gedcf2.fsf@gnu.org> (raw)
In-Reply-To: <200708132331.l7DNV8s17892@f7.net> (karl@freefriends.org)

> Date: Mon, 13 Aug 2007 18:31:08 -0500
> From: karl@freefriends.org (Karl Berry)
> 
> As I wrote in other msgs, it is quite painful to discover and turn off
> all the face names individually.  (E.g., C-u C-x = isn't usable with
> minibuffer text, mode lines, etc.)

Did you actually try to use "C-u C-x =" in the minibuffer?  It works
for me.

But I agree that discovering the faces is a job best avoided.

> If you feel it's inappropriate for (global-font-lock-mode 0) to turn off
> such things, then how about another feature that turns off all these
> colorizations and such things?  As in, (black-and-white-emacs) ...

I think it makes a lot of sense to have either global-font-lock-mode
turn off all faces (perhaps with minor exceptions, like mode line and
fringe?) or to have another option to do that in one go.

> P.S. I also noticed that the startup screen and *scratch* buffer text are
> colorized, although I was turning off font-lock on the cmd line:
>   emacs-22.1 -q --no-site --eval "(global-font-lock-mode 0)"

Try doing that in one of the hooks defined by startup.el, it could be
that the command-line args are processed too late for them to have any
effect on the initial display.

  reply	other threads:[~2007-08-14  3:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200708112124.l7BLOgG19369@f7.net>
2007-08-12 17:56 ` can't turn off font-lock Richard Stallman
2007-08-12 19:53   ` Stefan Monnier
2007-08-12 21:48     ` Karl Berry
2007-08-12 22:11       ` Stefan Monnier
2007-08-12 22:54         ` Karl Berry
2007-08-12 23:15           ` Andreas Schwab
2007-08-13  2:38             ` Eli Zaretskii
2007-08-12 23:24           ` Juri Linkov
2007-08-13 22:14             ` Karl Berry
2007-08-13 23:27               ` Juri Linkov
2007-08-13  2:37           ` Eli Zaretskii
2007-08-13  5:00           ` Richard Stallman
2007-08-13 19:56           ` Eli Zaretskii
2007-08-12 22:44       ` Alfred M. Szmidt
2007-08-13  5:01     ` Richard Stallman
2007-08-12 21:48   ` Karl Berry
2007-08-13  5:00     ` Richard Stallman
2007-08-12 22:54   ` Karl Berry
2007-08-13  2:31     ` Eli Zaretskii
2007-08-13  5:00     ` Richard Stallman
2007-08-13 23:31       ` Karl Berry
2007-08-14  3:26         ` Eli Zaretskii [this message]
2007-08-14 16:06         ` Richard Stallman
2007-08-13 23:31       ` Karl Berry
2007-08-13 23:51         ` Stefan Monnier
2007-08-14 16:06           ` Richard Stallman
2007-08-14 16:06         ` Richard Stallman

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=uy7gedcf2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).