* bug#31032: can't read emacs - unusable
@ 2018-04-02 21:07 K Richard Pixley
2018-04-02 22:40 ` Noam Postavsky
2018-04-02 23:31 ` Noam Postavsky
0 siblings, 2 replies; 6+ messages in thread
From: K Richard Pixley @ 2018-04-02 21:07 UTC (permalink / raw)
To: 31032; +Cc: K Richard Pixley
I'm trying to start emacs on a random machine, some random, unknown
configuration, and I can't read it because of the color settings.
What's the command line option to tell it to stop using color?
Many people can't discriminate colors unless they're set up by a color
professional who understands color vision. Most aren't. And I can't see it.
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.
Incredibly frustrating.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#31032: can't read emacs - unusable
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
1 sibling, 1 reply; 6+ messages in thread
From: Noam Postavsky @ 2018-04-02 22:40 UTC (permalink / raw)
To: K Richard Pixley; +Cc: K Richard Pixley, 31032
K Richard Pixley <pixleyr@google.com> writes:
> I'm trying to start emacs on a random machine, some random, unknown
> configuration, and I can't read it because of the color settings.
>
> What's the command line option to tell it to stop using color?
Do you mean in the terminal? Try '--color=never'.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#31032: can't read emacs - unusable
2018-04-02 22:40 ` Noam Postavsky
@ 2018-04-02 23:01 ` K Richard Pixley
0 siblings, 0 replies; 6+ messages in thread
From: K Richard Pixley @ 2018-04-02 23:01 UTC (permalink / raw)
To: Noam Postavsky; +Cc: K Richard Pixley, 31032
On 04/02/2018 03:40 PM, Noam Postavsky wrote:
> K Richard Pixley <pixleyr@google.com> writes:
>
>> I'm trying to start emacs on a random machine, some random, unknown
>> configuration, and I can't read it because of the color settings.
>>
>> What's the command line option to tell it to stop using color?
> Do you mean in the terminal? Try '--color=never'.
Didn't help. Still colored.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#31032: can't read emacs - unusable
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:31 ` Noam Postavsky
2018-04-03 0:01 ` K Richard Pixley
1 sibling, 1 reply; 6+ messages in thread
From: Noam Postavsky @ 2018-04-02 23:31 UTC (permalink / raw)
To: K Richard Pixley; +Cc: K Richard Pixley, 31032
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)
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#31032: can't read emacs - unusable
2018-04-02 23:31 ` Noam Postavsky
@ 2018-04-03 0:01 ` K Richard Pixley
2018-04-07 1:53 ` Noam Postavsky
0 siblings, 1 reply; 6+ messages in thread
From: K Richard Pixley @ 2018-04-03 0:01 UTC (permalink / raw)
To: Noam Postavsky; +Cc: K Richard Pixley, 31032
Thank you.
Looks like I needed: emacs -Q -nw --color=never.
I can chase it down from there.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#31032: can't read emacs - unusable
2018-04-03 0:01 ` K Richard Pixley
@ 2018-04-07 1:53 ` Noam Postavsky
0 siblings, 0 replies; 6+ messages in thread
From: Noam Postavsky @ 2018-04-07 1:53 UTC (permalink / raw)
To: K Richard Pixley; +Cc: K Richard Pixley, 31032
close 31032
quit
K Richard Pixley <pixleyr@google.com> writes:
> Looks like I needed: emacs -Q -nw --color=never.
>
> I can chase it down from there.
Okay, closing.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-04-07 1:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2018-04-03 0:01 ` K Richard Pixley
2018-04-07 1:53 ` Noam Postavsky
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).