X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 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: <416096c60908312242g39e38fe5s5dbe299e84f6afd8@mail.gmail.com> Date: Tue, 1 Sep 2009 17:45:20 +0100 Message-ID: <416096c60909010945q1673b591w316629d54d606310@mail.gmail.com> Subject: Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support! From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Andrew Schulman: >> > TERM=3Dxterm-256color screen -T screen-256color >> >> Instead of specifying -T screen-256color every time, one can just put >> 'term screen-256color' into .screenrc. =C2=A0I'll update the docs to sho= w this >> when I make the release current. > > Is there any reason that I shouldn't put this command into the default > /etc/screenrc file? 'fraid so. Prompted by this thread I wondered the same thing about mintty: why not set TERM to "xterm-256color" by default? Answer: because /etc/termcap doesn't know about it, and other programs that read the TERM variable might not recognise it either. Furthermore, user startup scripts that compare TERM to "xterm" or "screen" would break. Shame. 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