From: Eli Zaretskii <eliz@gnu.org>
To: chohag@jtan.com
Cc: 69598@debbugs.gnu.org, chohag@jtan.com
Subject: bug#69598: 29.2; colour support based on $TERM value not terminfo database
Date: Fri, 08 Mar 2024 21:50:01 +0200 [thread overview]
Message-ID: <86edckzeom.fsf@gnu.org> (raw)
In-Reply-To: <202403081852.428IqU5m307520@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 "Fri, 08 Mar 2024 17:09:51 +0200."
> Date: Fri, 08 Mar 2024 18:52:28 +0000
>
> > So you now agree with me that a terminal file in lisp/term is needed
> > for this situation? Or are there issues that are still unaccounted
> > for, as far as color support is concerned?
>
> I don't agree.
In that case, we will have to agree to disagree, sorry.
> In short, if emacs only supports colour (or any other feature) on
> specific terminals it knows about in advance, it should say so and
> not imply that a terminfo or termcap capability is sufficient.
Support for colors beyond the basic 8 is very specific to terminals.
Emacs solves this problem by relying on the name of the terminal. So
any new terminal has to abide by this protocol. That's how this stuff
works in Emacs.
next prev parent reply other threads:[~2024-03-08 19:50 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
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 [this message]
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=86edckzeom.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 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.