Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <200308151936.UAA11794@aps5.ph.bham.ac.uk> Date: Fri, 15 Aug 2003 20:34:42 +0100 (BST) From: "Dr.D.J.Picton" Reply-To: "Dr.D.J.Picton" Subject: Re: Various shell problems To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: mC+bvzJdrhm40XossJoQug== > Date: Fri, 15 Aug 2003 14:23:06 -0400 > From: Larry Hall > To: "Dr.D.J.Picton" > CC: cygwin AT cygwin DOT com > Subject: Re: Various shell problems > > > 2. SHELL environment variable problem. > > For some reason, the bash shell tends to drop the SHELL variable from the > > environment, causing a variety of problems. I fixed this with a new > > startup script (/etc/bash.bash_env) which issues 'export SHELL', and by > > contriving (via the BASH_ENV environment variable and .bashrc scripts) that > > all bash shells will use the script. > > > This is a change in bash behavior. It's intentional. It's not something > new though. It's at least a year old. You can check the email archives > for the bash announcement on this issue and/or the subsequent reports of > "bugs" from this behavior change. Thank you for clarifying this. I obviously need to do my homework more thoroughly in the future! The ftp problem occurs because the /bin/sh shell is called with $0='-sh' (whereas other shells have $0='+bash' etc and therefore presumably don't regard themselves as login shells). I'll modify profile to detect the situation and avoid doing cd $HOME. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/