From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!
Date: Tue, 01 Sep 2009 12:53:41 -0400
Message-ID: <17kq9510j9kst8dcpc516i8ce10n64nlta@4ax.com>
References: <announce.gaeo95tesfohfdbn4m8snu1afforj074rg@4ax.com> 	 <416096c60908312242g39e38fe5s5dbe299e84f6afd8@mail.gmail.com> 	 <loom.20090901T165202-526@post.gmane.org> 	 <loom.20090901T182021-340@post.gmane.org> <416096c60909010945q1673b591w316629d54d606310@mail.gmail.com>
In-Reply-To: <416096c60909010945q1673b591w316629d54d606310@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: 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. =A0I'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?
>=20
> 'fraid so. Prompted by this thread I wondered the same thing about
> mintty: why not set TERM to "xterm-256color" by default?
>=20
> 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.

You're talking about setting e.g. TERM=3Dxterm-256color in the environment =
by
default, but I was asking whether it would cause any harm to put 'term
screen-256color' into the default /etc/screenrc.  Know any reason that I
shouldn't?

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