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, 30 Apr 2001 15:10:24 -0400 From: Jason Tishler To: cygwin Subject: Re: bash 2.05 broken -i flag Message-ID: <20010430151024.A577@dothill.com> Mail-Followup-To: cygwin References: <200104201719 DOT NAA13922 AT ny DOT dothill DOT com> <20010425103958 DOT B173 AT dothill DOT com> <20010429191529 DOT B22095 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010429191529.B22095@cygbert.vinschen.de>; from cygwin@cygwin.com on Sun, Apr 29, 2001 at 07:15:29PM +0200 Organization: Dot Hill Systems Corp. Corrina, On Sun, Apr 29, 2001 at 07:15:29PM +0200, Corinna Vinschen wrote: > On Wed, Apr 25, 2001 at 10:39:58AM -0400, Jason Tishler wrote: > > Invoking bash 2.05-2 with the "-i" option does not seem to cause problems: > > > > $ bash -i > > $ vi > > $ > > > > But, if the first line of a shell script contains "-i" then bad things > > happen: > > > > [snip] > > Just to let you know, I have sent a note to Chet Ramey since I have > no clue why that happens. Hope to get an answer or patch soon. Thank you *very* much for the status update -- I was starting to wonder that it must be user error, bad setup, etc. I will patiently continue to use 2.04-7a until there is a resolution. Thanks, Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason DOT Tishler AT dothill DOT com Hazlet, NJ 07730 USA WWW: http://www.dothill.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple