From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ncurses: Install 256 color terminfo files
Date: Thu, 28 Dec 2017 23:32:35 +0100 [thread overview]
Message-ID: <20171228233235.49005288@windsurf> (raw)
In-Reply-To: <20171220020624.22252-1-tpiepho@impinj.com>
Hello,
On Tue, 19 Dec 2017 18:06:24 -0800, Trent Piepho wrote:
> There are three 256 color terminfo files that buildroot only installs if
> ncurses is configured with wide character support, which also enables
> ext-color. There is a fourth 256 color terminfo file and does not depend
> on wchar suport and is always installed.
>
> This changes that to always install all four 256 color terminfo files.
The patch looks fine, but I'm confused when you say "all four 256 color
terminfo files", while the patch only changes the installation of three
terminfo files. Could you explain ?
> When ncurses has ext-colors enabled,it allows 256 fg and bg colors at the
> same time. Without ext-colors, it is still possible to use the 256 color
> terminfo files and one can get a combination of fb and bg colors that
> equals up to 256, e.g. 256 fg colors on one background or 16 fg and 16 bg
> colors.
>
> In short, the 256 color files work fine without wchar or ext-color support
> and support more colors than the normal xterm, etc. terminfo files. It's
> common today for the default terminal to use xterm-256color and it's nice
> if thinks like vim and top work out of the box.
>
> Signed-off-by: Trent Piepho <tpiepho@impinj.com>
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-28 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 2:06 [Buildroot] [PATCH] ncurses: Install 256 color terminfo files Trent Piepho
2017-12-28 22:32 ` Thomas Petazzoni [this message]
2017-12-28 22:58 ` Trent Piepho
2018-01-07 22:52 ` Thomas Petazzoni
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=20171228233235.49005288@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox