From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Forcing emacs to not use 256 colors
Date: Sat, 01 Jul 2023 11:07:01 +0300 [thread overview]
Message-ID: <83y1k0qcm2.fsf@gnu.org> (raw)
In-Reply-To: <ZJ/Mzg4aYifcc9LS@tuxteam.de> (tomas@tuxteam.de)
> Date: Sat, 1 Jul 2023 08:50:54 +0200
> From: <tomas@tuxteam.de>
>
> > > > 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?
>
> I think you're being a bit unfair here: the original problem
> description is perfectly valid and John's observation seems
> quite adequate.
I didn't say the problem is invalid. I just said that assuming the
user needs to customize _all_ of the faces is an exaggeration of the
problem facing the user. I don't think I deserve this kind of cold
shower just because I have a different perspective on this. I do my
share of face customizations, so I know something about what's
involved.
And I only wrote that as an aside, after trying to answer the specific
question the user asked.
Again, it's okay to disagree, but please do so in a way that respects
differing opinions, which means, among the rest, not to hint they are
invalid, "unfair", or any other such derogation.
> For someone who has been happy with a set of defaults up to
> now (for whatever set of reasons: habituation may be in there),
> it can be jarring if those defaults change. That user perhaps
> doesn't know how Emacs manages faces. Finding their way to
> "customize the faces they care about" is the first challenge.
> Finding the set of those may develop to a happy game of whack-
> a-mole.
If the OP doesn't know how to customize faces, or how to find which
face is used at a given location, they can always ask; this is what
this list is for. Lecturing users about things they already know is
also sometimes taken as a patronizing offense, so I prefer to wait for
specific questions. I don't see why this approach should be a
problem, but if you or someone else prefers to post the detailed
information without waiting for questions, please do.
> > > 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...
>
> I seriously hope this is tongue-in-cheek.
It wasn't; it was a good-faith suggestion to consider whether the
defaults are really disliked or merely unusual (in which case maybe
they just take some getting used to).
And I wonder why you saw it appropriate to express that "hope" in a
public post in the first place. This is supposed to be a forum where
each one tries to help those who asks questions as best as they can,
and I don't think my attempts to do so in this case were not useful,
let alone intentionally so, to deserve such rebuttals.
next prev parent reply other threads:[~2023-07-01 8:07 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
2023-07-01 6:50 ` tomas
2023-07-01 8:07 ` Eli Zaretskii [this message]
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=83y1k0qcm2.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.