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: Fri, 16 Nov 2001 13:03:25 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: bash-2.05a-1 Message-ID: <20011116130325.B16860@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <200111161019 DOT fAGAJui15314 AT loony DOT cygnus DOT com> <3BF4F806 DOT C5530DAA AT iee DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BF4F806.C5530DAA@iee.org>; from dwsharp@iee.org on Fri, Nov 16, 2001 at 11:27:02AM +0000 On Fri, Nov 16, 2001 at 11:27:02AM +0000, Don Sharp wrote: > > > Corinna Vinschen wrote: > > > > I've updated the version of bash in cygwin/latest to 2.05a-1. > > > > This is the official version 2.05a as announced yesterday on > > the Cygwin mailing list by Chet Ramey. > > > ... snip ... > > I now get > > dircolors: no SHELL environment variable, and no shell type option given > dircolors: no SHELL environment variable, and no shell type option given > > It seems that the new bash doesn't provide dircolors with a SHELL > environment variable. Is this a dircolors or bash effect? Honestly, I don't know. I don't even understand the question. I'm maintaining bash but I'm using tcsh privatly so I need some more hints. It would even be better you can track that down by yourself and then just blame the source of the problem :-) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/