all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: chohag--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69598@debbugs.gnu.org, chohag@jtan.com
Subject: bug#69598: 29.2; colour support based on $TERM value not terminfo database
Date: Thu, 07 Mar 2024 18:31:20 +0000	[thread overview]
Message-ID: <202403071831.427IVMWs374766@zeus.jtan.com> (raw)
In-Reply-To: <86sf120w9y.fsf@gnu.org>

Eli Zaretskii writes:
> > 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).
>
> 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,

If there's something you would like me to look for then I can but
I am highly sceptical of the idea that it is isolated to something
unique about my computers here.

Besides you can see clearly in term.c that there are no references
to xterm in the strings and hopefully none hidden behind macros
(there is one to xterm+direct in a comment describing where hard-coded
defaults are from, which is one of the xterm-direct building blocks),
so whatever is going wrong is likely to be somewhere else, such as
a misunderstanding deeper within the emacs runtime.

> and see what's going on there on your system.  Just from the

Systems. Plural. Linux and BSD. I could probably open an xterm on
something else somehow but the chance of the same problem on two
distinct systems being caused by a local issue is very low.

Did you confirm presence of the bug with the transcript I provided?

> information you provided, it is very hard to guess what could be the
> culprit.

It's a lot harder for me. I only use emacs.

What more information do you need? Here's another bit from a quick
test while writing this email (in the unadulterated-Debian xterm
that's still open):

        $ echo 'xterm-naughty|Naughty Term,use=xterm-direct,' >> fancy.info
        $ tic fancy.info
        $ export TERM=xterm-naughty
        $ emacs -nw

That emacs displayed all the colours, so it's not 'xterm-direct'
in $TERM that emacs is treating magically, it's 'xterm' (naughty-xterm
lists 8 colours, so probably make that /^xterm/).

Matthew






  reply	other threads:[~2024-03-07 18:31 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
2024-03-07 18:31       ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202403071831.427IVMWs374766@zeus.jtan.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=69598@debbugs.gnu.org \
    --cc=chohag@jtan.com \
    --cc=eliz@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.