From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Using Emacs in fbterm.
Date: Mon, 29 Aug 2022 20:33:13 +0300 [thread overview]
Message-ID: <83czcjvtt2.fsf@gnu.org> (raw)
In-Reply-To: <YwzsHA9ctqFVmRTj@ACM> (message from Alan Mackenzie on Mon, 29 Aug 2022 16:41:00 +0000)
> Date: Mon, 29 Aug 2022 16:41:00 +0000
> From: Alan Mackenzie <acm@muc.de>
>
> There is a problem with colours in Emacs in fbterm. When one does M-:
> (defined-colors) it prints a list of just eight colours, black, red,
> ...., white.
>
> However, the face constructing mechanism seems to assume more than eight
> colours, and this seems buggy.
Face constructing makes no such assumptions. If the colors defined
for the face are not directly supported by the terminal (in this case,
not in the 8 colors), Emacs uses color-translation to find the closest
color that is supported. See tty-colors.el. If this translation
doesn't produce satisfactory results, the face colors need to be
either:
. changed such that (a) on color-rich terminals the colors are
similar, but (b) on 8-color terminals we get better results; or
. the face definition should be changed to have a separate setting
of colors for terminals with 8 colors
> The face hi-green, for example, rather than having background
> "green" gets "light green". This appears on the terminal as dark
> yellow, which is clearly wrong.
Why do you think it's wrong? Given that yellow is closer to hi-green
(judging by its RGB components) than green, I see nothing wrong here.
> Also the face mode-line-inactive is indistinguishable from the default
> face
??? It should be the same as mode-line face of the active mode line.
I wonder how come it's the same as the default in your case. Is that
in "emacs -Q"?
next prev parent reply other threads:[~2022-08-29 17:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 16:41 Using Emacs in fbterm Alan Mackenzie
2022-08-29 17:33 ` Eli Zaretskii [this message]
2022-08-29 18:44 ` Alan Mackenzie
2022-08-29 18:53 ` Eli Zaretskii
2022-08-29 18:54 ` Gregory Heytings
2022-08-29 18:59 ` Eli Zaretskii
2022-08-29 19:29 ` Gregory Heytings
2022-08-29 19:42 ` Eli Zaretskii
2022-08-29 19:45 ` Gregory Heytings
2022-08-29 19:55 ` Gregory Heytings
2022-08-29 19:34 ` Andreas Schwab
2022-08-29 19:43 ` Gregory Heytings
2022-08-29 19:52 ` Andreas Schwab
2022-08-29 20:27 ` Gregory Heytings
2022-08-29 20:35 ` Alan Mackenzie
2022-08-29 20:52 ` Gregory Heytings
2022-08-29 22:28 ` Gregory Heytings
2022-08-30 11:32 ` Eli Zaretskii
2022-08-30 12:04 ` Gregory Heytings
2022-08-30 12:10 ` Eli Zaretskii
2022-08-30 21:10 ` Gregory Heytings
2022-08-30 13:16 ` Stefan Monnier
2022-08-30 15:37 ` Gregory Heytings
2022-08-30 18:26 ` Stefan Monnier
2022-08-30 21:20 ` Gregory Heytings
2022-08-30 21:56 ` Stefan Monnier
2022-08-30 22:07 ` Gregory Heytings
2022-09-04 2:59 ` Stefan Monnier
2022-08-29 18:50 ` Gregory Heytings
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=83czcjvtt2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@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 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).