unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: K Richard Pixley <pixleyr@google.com>
Cc: K Richard Pixley <rich@noir.com>, 31032@debbugs.gnu.org
Subject: bug#31032: can't read emacs - unusable
Date: Mon, 02 Apr 2018 19:31:00 -0400	[thread overview]
Message-ID: <87vad9nq2z.fsf@gmail.com> (raw)
In-Reply-To: <995ce322-8a59-5314-116d-72efe126efa8@google.com> (K. Richard Pixley's message of "Mon, 2 Apr 2018 14:07:54 -0700")

K Richard Pixley <pixleyr@google.com> writes:

> On my private configurations, I can set them to turn off font-lock
> mode, but from the command line, even --eval='(global-font-lock-mode
> 0)' doesn't seem to be working.

Perhaps the configuration explicitly enables font-lock?  Why not use -Q
so you don't have to deal with random configurations?

    emacs -Q --eval='(global-font-lock-mode 0)'

I don't there is any command line option to disable colour in graphical
mode.  Possibly you could disable font-lock later, e.g.,

    emacs --eval='(add-hook (quote after-init-hook) (lambda () (global-font-lock-mode 0)))'

To completely get rid of all colour, you could evaluate:

    (dolist (face (face-list))
      (when (face-foreground face)
        (set-face-foreground face 'unspecified))
      (when (face-background face)
        (set-face-background face 'unspecified)))

(again, this would probably have to be done in the after-init-hook, if
the configuration makes its own colour settings to faces)





  parent reply	other threads:[~2018-04-02 23:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 21:07 bug#31032: can't read emacs - unusable K Richard Pixley
2018-04-02 22:40 ` Noam Postavsky
2018-04-02 23:01   ` K Richard Pixley
2018-04-02 23:31 ` Noam Postavsky [this message]
2018-04-03  0:01   ` K Richard Pixley
2018-04-07  1:53     ` Noam Postavsky

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=87vad9nq2z.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31032@debbugs.gnu.org \
    --cc=pixleyr@google.com \
    --cc=rich@noir.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 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).