unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: Using Emacs in fbterm.
Date: Mon, 29 Aug 2022 19:55:26 +0000	[thread overview]
Message-ID: <a77ca586b680148db42c@heytings.org> (raw)
In-Reply-To: <a77ca586b62b6b73b534@heytings.org>


>>>> What does the terminfo DB say about commands to set color on fbterm?
>>> 
>>> Here's the comparison of the relevant entries between linux and 
>>> fbterm. I don't know where the fbterm entries come from, they seem to 
>>> be based on some patched version.
>> 
>> Not surprisingly, the differences are in color commands.
>
> I guess the safest fix is to add an additional note about this in the 
> FAQ entry?
>

And the details are in the manpage:

FbTerm supports xterm's 256 color mode extension. The first 16 colors are 
the default terminal colors. Additionally, there's a 6x6x6 color cube, and 
24 grayscale tones.  But xterm's 256 color escape sequences conflict with 
the linux sequences implemented by FbTerm, so private escape sequences 
were introduced to support this feature:

ESC [ 1 ; n }              set foreground color to n (0 - 255)
ESC [ 2 ; n }              set background color to n (0 - 255)
ESC [ 3 ; n ; r ; g ; b }  set color n to (r, g, b) ,  n, r, g, b all in (0 - 255)

A new terminfo database entry named "fbterm" was added to use these 
private sequences, all program based on terminfo should work with it.  By 
default, FbTerm sets environment variable "TERM" to value "linux", user 
need run "TERM=fbterm /path/to/program" to enable 256 color mode.

Apparently some distros have chosen to enable that 256 color mode by 
default.



  reply	other threads:[~2022-08-29 19:55 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
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 [this message]
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=a77ca586b680148db42c@heytings.org \
    --to=gregory@heytings.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --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).