From: Thomas Dickey <dickey@radix.net>
Cc: stktrc <stktrc@yahoo.com>, emacs-devel@gnu.org
Subject: Re: Support for XTerm's 256-color extension?
Date: Thu, 6 May 2004 06:05:02 -0400 [thread overview]
Message-ID: <20040506100501.GA19579@saltmine.radix.net> (raw)
In-Reply-To: <uwu3qoy8e.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1478 bytes --]
On Thu, May 06, 2004 at 08:39:45AM +0200, Eli Zaretskii wrote:
> > From: stktrc <stktrc@yahoo.com>
> > Date: 05 May 2004 21:43:49 +0300
> >
> > > What is the value of "NC" for the 256-color xterm on your system?
> >
> > I found out it was 32 (disable bold), which was the cause for not
> > getting bold, i.e., you were on the right track.
> >
> > Looking at the definition of xterm-256color in the terminfo file in
> > xterm-187, there is ncv#32. There is a comment before the definition
> > that seems to provide some information on why ncv is 32, but I do not
> > understand it fully. See below.
> >
> > #
> > # OPT_PC_MODE should be settable with OSC, and the init for this
> > # should turn it off; then ncv could be 0.
> > # This uses RGB values 0..1000
> > xterm-256color|xterm with 256 colors,
> > ccc,
> > colors#256,
> > ncv#32,
> > [rest, not as interesting, left out]
> >
> > I made a custom terminfo entry that extends xterm-256color with ncv#0,
> > so that bold now works.
> >
> > Should this really be necessary?
>
> It shouldn't, but I'm guessing that whoever wrote that entry had
> his/her reasons.
>
> I'm CC'ing T. Dickey in the hope that he could help us understand this
> issue.
OPT_PC_MODE refers to the optional mapping of bold as brighter colors.
If he doesn't want/need that, then it doesn't matter.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
[-- Attachment #1.2: Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
prev parent reply other threads:[~2004-05-06 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <i56y8o8m0nx.fsf@mao.acc.umu.se>
2004-05-04 21:33 ` Support for XTerm's 256-color extension? Dan Nicolaescu
[not found] ` <i56k6zr511w.fsf@mao.acc.umu.se>
2004-05-05 6:39 ` Eli Zaretskii
[not found] ` <i56brl2lnoa.fsf@mao.acc.umu.se>
2004-05-06 6:39 ` Eli Zaretskii
2004-05-06 10:05 ` Thomas Dickey [this message]
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=20040506100501.GA19579@saltmine.radix.net \
--to=dickey@radix.net \
--cc=emacs-devel@gnu.org \
--cc=stktrc@yahoo.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).