all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Forcing emacs to not use 256 colors
Date: Fri, 30 Jun 2023 21:58:20 +0300	[thread overview]
Message-ID: <83leg0sroz.fsf@gnu.org> (raw)
In-Reply-To: <CAJnXXogTWy-6W-=SSO4PCDY6X+XD8oq-ibF3u6nJz6dNTN+10g@mail.gmail.com> (message from John Yates on Fri, 30 Jun 2023 11:14:28 -0400)

> From: John Yates <john@yates-sheets.org>
> Date: Fri, 30 Jun 2023 11:14:28 -0400
> Cc: help-gnu-emacs@gnu.org
> 
> > If you don't like the default colors themselves, isn't it better to
> > customize the faces to use the colors you like?
> 
> Properly done, that is an enormous undertaking.

Not if you only ever customize the faces you care about.  Let's not
gratuitously exaggerate the problem, okay?

> Just take a look at the work Protesilaos has put into creating
> themes covering large numbers of emacs packages.

Themes customize most if not all faces, something individual users
will never need to do.

Of course, the best is to just use the defaults: they are, after all,
well thought-out...



  reply	other threads:[~2023-06-30 18:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230628115134.6f5874ca@fecfc4134a3d>
2023-06-28 15:51 ` Forcing emacs to not use 256 colors Tom Noonan II
2023-06-30 12:00   ` Eli Zaretskii
2023-06-30 15:14     ` John Yates
2023-06-30 18:58       ` Eli Zaretskii [this message]
2023-07-01  6:50         ` tomas
2023-07-01  8:07           ` Eli Zaretskii
2023-07-02  8:04             ` tomas
2023-07-02  8:23               ` Eli Zaretskii
2023-07-02  8:47   ` Gregory Heytings
     [not found]     ` <20230704160635.306eedbe@fecfc4134a3d>
2023-07-04 20:06       ` Tom Noonan II
2023-07-05  4:03         ` Platon Pronko

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83leg0sroz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.