X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE
X-Spam-Check-By:	sourceware.org
Message-ID:	<BAY157-w64AE820D2F752B0BC9AE8E8D540@phx.gbl>
From:	"Anna Z." <siana DOT sg AT live DOT de>
To:	<cygwin AT cygwin DOT com>
Subject:	screen 4.0.3-5 does not respect $SHELL
Date:	Tue, 12 Oct 2010 18:26:01 +0200
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Hello.
I'm experiencing the following issue.
Initially SHELL=3D/bin/bash when using a link in start menu.From initial ba=
sh prompt, i start screen, fresh session. There all kinds of bash misbehavi=
or occur, including ~/.bashrc having no effect. Apparent reason for that is=
 that $SHELL becomes /bin/sh instead of /bin/bash within screen.
A workaround is to start screen asscreen -s /bin/bashor have shell specifie=
d in .screenrc. Then bash works as expected. That screen does not respect $=
SHELL seems to be a bug though.
Thanks to jturney from #cygwin for helping me pinpoint the problem.
-anna=20=09=09=20=09=20=20=20=09=09=20=20

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

- Raw text -