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: Sun, 29 Apr 2001 19:15:29 +0200 From: Corinna Vinschen To: cygwin Subject: Re: bash 2.05 broken -i flag Message-ID: <20010429191529.B22095@cygbert.vinschen.de> Mail-Followup-To: cygwin References: <200104201719 DOT NAA13922 AT ny DOT dothill DOT com> <20010425103958 DOT B173 AT dothill DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010425103958.B173@dothill.com>; from Jason.Tishler@dothill.com on Wed, Apr 25, 2001 at 10:39:58AM -0400 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: > > $ cat foo.sh > #! /bin/bash -i > echo hello > $ foo.sh > $ # *** Note no output -- hello should have been echoed *** > $ vi > bash: [360: 3] tcsetattr: Not a character device > > [1]+ Stopped vi > $ stty sane > $ jobs > [1]- Stopped vi > [2]+ Stopped stty sane 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. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple