X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Andrew Schulman <schulman.andrew@epa.gov>
Subject:  Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!
Date: Tue, 1 Sep 2009 16:29:24 +0000 (UTC)
Lines: 17
Message-ID:  <loom.20090901T182021-340@post.gmane.org>
References:  <announce.gaeo95tesfohfdbn4m8snu1afforj074rg@4ax.com> <416096c60908312242g39e38fe5s5dbe299e84f6afd8@mail.gmail.com> <loom.20090901T165202-526@post.gmane.org>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

> > TERM=xterm-256color screen -T screen-256color
> 
> Instead of specifying -T screen-256color every time, one can just put
> 'term screen-256color' into .screenrc.  I'll update the docs to show this
> when I make the release current.

Is there any reason that I shouldn't put this command into the default
/etc/screenrc file?  Are there terminal types for which it would cause problems?

I just tried this with a DOS terminal, which doesn't support 256 colors AFAIK. 
It didn't make any difference that I could tell.

Maybe I'll put out another test release with that change, and see if anyone
complains.

A.



--
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