all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Platon Pronko <platon7pronko@gmail.com>
To: Tom Noonan II <tom@tjnii.com>, Gregory Heytings <gregory@heytings.org>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Forcing emacs to not use 256 colors
Date: Wed, 5 Jul 2023 08:03:39 +0400	[thread overview]
Message-ID: <c24b869a-f78f-7e9a-4abf-c8a590fa7ff0@gmail.com> (raw)
In-Reply-To: <010001892283a818-faef1ada-0fd7-475b-a92a-4611c66a6e73-000000@email.amazonses.com>

On 2023-07-05 00:06, Tom Noonan II wrote:
> This my current workaround but I'd prefer to find a solution that's
> limited to emacs, if possible.  This seems like something I should be
> able to configure, but I'm not familiar enough with the colorization
> internals (or lisp) to know where to start.

Maybe `alias emacs="TERM=xterm16-color emacs"`?

It's looks like the simplest approach, the alternative being going very deep into Emacs internals (and probably recompiling it with your own patches, as terminal color selection is probably done in C code).

-- 
Best regards,
Platon Pronko
PGP 2A62D77A7A2CB94E




      reply	other threads:[~2023-07-05  4:03 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
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 [this message]

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=c24b869a-f78f-7e9a-4abf-c8a590fa7ff0@gmail.com \
    --to=platon7pronko@gmail.com \
    --cc=gregory@heytings.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tom@tjnii.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 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.