X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 1 Sep 2009 06:42:16 +0100 Message-ID: <416096c60908312242g39e38fe5s5dbe299e84f6afd8@mail.gmail.com> Subject: Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support! From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Andrew Schulman: > Instructions for starting screen with 256 color support are in > /usr/share/doc/screen/README.Cygwin. =C2=A0In brief, you have to invoke s= creen > as > > TERM=3Dscreen-256color screen I don't think that's quite right. Screen needs to be told what terminal it is itself running in. This means "xterm-256color" for xterm, PuTTY and MinTTY, and "rxvt-256color" for rxvt. Inside screen, however, the TERM variable does need to be set to "screen-256color" to tell termcap/terminfo-using programs that they are running in a 256-color-enabled screen. The -T option can be used for that. So, for example: TERM=3Dxterm-256color screen -T screen-256color 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