From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ncurses: add xterm-256color to terminfo-base
Date: Thu, 11 Jul 2013 20:29:07 -0500 [thread overview]
Message-ID: <51DF5BE3.8090803@windriver.com> (raw)
In-Reply-To: <1373590411-6276-1-git-send-email-sgw@linux.intel.com>
On 7/11/13 7:53 PM, Saul Wold wrote:
> This is to address the buildtools-tarball still having problems with certain
> xterms
>
> [YOCTO #4835]
This is a reasonable workaround, but the real problem seems to be that nativesdk
python/ncurses return crap (strings with embedded control codes) when they don't
know what the TERM is. I think this is the real underlying problem that needs
to be fixed, unfortunately I have no idea what the cause is.
The alternative is to somehow enforce terminal settings when using the
buildtools-tarball are one of the known terminals.
--Mark
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/recipes-core/ncurses/ncurses.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/ncurses/ncurses.inc b/meta/recipes-core/ncurses/ncurses.inc
> index 2ed1bba..671daf8 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -174,7 +174,7 @@ shell_do_install() {
>
> # include some basic terminfo files
> # stolen ;) from gentoo and modified a bit
> - for x in ansi console dumb linux rxvt screen sun vt{52,100,102,200,220} xterm-color xterm-xfree86
> + for x in ansi console dumb linux rxvt screen sun vt{52,100,102,200,220} xterm-color xterm-xfree86 xterm-256color
> do
> local termfile="$(find "${D}${datadir}/terminfo/" -name "${x}" 2>/dev/null)"
> local basedir="$(basename $(dirname "${termfile}"))"
>
prev parent reply other threads:[~2013-07-12 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 0:53 [PATCH] ncurses: add xterm-256color to terminfo-base Saul Wold
2013-07-12 1:29 ` Mark Hatle [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51DF5BE3.8090803@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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.
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.