X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: GNU screen not redrawing properly Date: Thu, 16 Jun 2011 20:33:06 -0400 Lines: 25 Message-ID: References: <20110613215328 DOT GA3260 AT icebox> <20110613234412 DOT GA3724 AT icebox> <20110614121229 DOT GA556 AT icebox> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > 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 ' 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. Eric, please see the discussion of 256-color mode in screen in /usr/share/doc/screen/README.Cygwin. It includes the proper terminal settings, as Andy described. Patches are welcome if more information is needed there. -- 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