Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 19 Nov 2001 01:43:01 +0100 From: "Gerrit P. Haase" X-Mailer: The Bat! (v1.53t) Business Reply-To: "Gerrit P. Haase" Organization: Esse keine toten Tiere X-Priority: 3 (Normal) Message-ID: <21130799183.20011119014301@familiehaase.de> To: cygwin AT cygwin DOT com Subject: Re: Problem with Bash 2.05a-2 In-Reply-To: <751E281AA9DED31194FA0090274DFFBC012E34FA@fmbex003.dsto.defence.gov.au> References: <751E281AA9DED31194FA0090274DFFBC012E34FA AT fmbex003 DOT dsto DOT defence DOT gov DOT au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Hops: 1 Hallo Shane, Am 2001-11-19 um 00:24 schriebst du: > G'day, > For some reason bash-2.05a-2 does not export the SHELL environment variable. > If you type "echo $SHELL" you get the right response of "/bin/bash", > however, if you type "env | grep SHELL" the variable is not to be seen. > bash-2.05-8 seems to be working correctly though and I have moved back to > this version. $ env | grep SHELL CONFIG_SHELL=sh SHELL=/usr/bin/bash $ cat ~/.bashrc | grep SHELL export CONFIG_SHELL=sh export SHELL=/usr/bin/bash Then it seems to be the reason why I export it myself... Ciao, Gerrit P. Haase mailto:gp AT familiehaase DOT de -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/