public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Cc: Eric Pruitt <eric.pruitt@gmail.com>
Subject: Re: GNU screen not redrawing properly
Date: Tue, 14 Jun 2011 12:32:00 -0000	[thread overview]
Message-ID: <BANLkTiki2q6fhUNbMhqXg-2_=kccbQG5ag@mail.gmail.com> (raw)
In-Reply-To: <20110614121229.GA556@icebox>

On 14 June 2011 13:12, Eric Pruitt wrote:
> Outside of screen, TERM=xterm. Inside of screen, well here is the relevant
> line from my bashrc; my screenrc doesn't have anything that would affect
> colors:
>
>    TERM=screen-256color GNU_SCREEN="active" screen -a -A -RR -T "$TERM" && \
>        screen -wipe || exit

Ah, this invokes screen itself with TERM=screen-256color, which tells
it to talk to the outside terminal as if that's another screen, which
is wrong. You want to be invoking it with TERM=xterm-256color instead
(which can be selected on the Terminal page of the mintty options).

Screen's '-T <term>' option determines the TERM variable inside
screen. Setting that to "screen-256color" to tell applications that
they're running in a 256-colour enabled screen does make sense.

Btw, screen emulates 256-colour mode inside a terminal that only
supports 16 colours, by mapping the colours appropriately. Of course
you'll still only get 16 actual colours, but it's still better than
having colour requests beyond the basic 16 ignored.

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2011-06-14 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 21:53 Eric Pruitt
2011-06-13 23:23 ` Chris Sutcliffe
2011-06-13 23:44   ` Eric Pruitt
2011-06-14  8:28     ` Andy Koppe
     [not found]       ` <20110614121229.GA556@icebox>
2011-06-14 12:32         ` Andy Koppe [this message]
2011-06-14 13:12           ` Eric Pruitt
2011-06-17  0:33           ` Andrew Schulman

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='BANLkTiki2q6fhUNbMhqXg-2_=kccbQG5ag@mail.gmail.com' \
    --to=andy.koppe@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=eric.pruitt@gmail.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.
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).