unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: chohag@jtan.com
Cc: 69598@debbugs.gnu.org
Subject: bug#69598: 29.2; colour support based on $TERM value not terminfo database
Date: Thu, 07 Mar 2024 19:47:05 +0200	[thread overview]
Message-ID: <86sf120w9y.fsf@gnu.org> (raw)
In-Reply-To: <202403071732.427HWear369011@zeus.jtan.com> (chohag@jtan.com)

> From: chohag@jtan.com
> cc: chohag@jtan.com, 69598@debbugs.gnu.org
> Comments: In-reply-to Eli Zaretskii <eliz@gnu.org>
>    message dated "Thu, 07 Mar 2024 08:47:37 +0200."
> Date: Thu, 07 Mar 2024 17:32:38 +0000
> 
> Eli Zaretskii writes:
> >
> >   ** Emacs can support 24-bit color TTY without terminfo database.
> >   If your text-mode terminal supports 24-bit true color, but your system
> >   lacks the terminfo database, you can instruct Emacs to support 24-bit
> >   true color by setting 'COLORTERM=truecolor' in the environment.  This is
> >   useful on systems such as FreeBSD which ships only with "etc/termcap".
> >
> >   *** Emacs will now use 24-bit colors on terminals that support "Tc" capability.
> >   This is in addition to previously-supported ways of discovering 24-bit
> >   color support: either via the "RGB" or "setf24" capabilities, or if
> >   the 'COLORTERM' environment variable is set to the value "truecolor".
> >
> > Did you try the COLORTERM=truecolor setting?
> 
> I did now, in a new non-xterm terminal which does display all colours
> in emacs if $TERM is xterm-direct, and no joy (only lists 8 colours).
> 
> I also performed this sequence on a linux (Debian 6.1.67-1 (2023-12-12))
> box in xterm (379) now that my cat has vacated it:
> 
>         $ export TERM=xterm-direct
>         $ emacs -nw                   # Version 28.2
>         $ echo 'fancy|Fancy Term,use=xterm-direct,' > fancy.info
>         $ tic fancy.info
>         $ export TERM=fancy
>         $ emacs -nw
> 
> In the first emacs, list-colors-display listed (I presume) 256
> colours. Certainly a lot and with the X names (it does not name
> them nicely if the terminal reports 256 colours). In the second it
> listed 8. Emacs has no configuration on that box (it's for compiling).
> 
> I recall testing the RGB capability late last night despite not
> seeing it documented anywhere and that did not work. I shall
> experiment with the Tc capability and RGB more carefully and see
> what effect they have nevertheless I think the above sequence now
> repeated on two distinct operating systems is quite telling.
> 
> Both systems have little or no customisation beyond the base image
> apart from installed packages. Certainly nothing that should affect
> terminfo (apart from running tic).

So I guess you will need to step with a debugger through the code in
term.c which discovers and initializes the color-related capabilities,
and see what's going on there on your system.  Just from the
information you provided, it is very hard to guess what could be the
culprit.

Thanks.






  reply	other threads:[~2024-03-07 17:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 23:01 bug#69598: 29.2; colour support based on $TERM value not terminfo database chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07  6:47 ` Eli Zaretskii
2024-03-07 17:32   ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 17:47     ` Eli Zaretskii [this message]
2024-03-07 18:31       ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 19:26         ` Eli Zaretskii
2024-03-07 19:59           ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 20:10             ` Eli Zaretskii
2024-03-07 21:45               ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 21:50                 ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-08  7:11                 ` Eli Zaretskii
2024-03-08 11:36                   ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-08 12:22                     ` Eli Zaretskii
2024-03-08 14:23                       ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-08 15:09                         ` Eli Zaretskii
2024-03-08 18:52                           ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-08 19:50                             ` Eli Zaretskii
2024-03-08 21:13                               ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-09  7:18                                 ` Eli Zaretskii
2024-03-21  8:33                                   ` Eli Zaretskii

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=86sf120w9y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69598@debbugs.gnu.org \
    --cc=chohag@jtan.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 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).