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 X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Wed, 31 Jan 2001 11:17:56 -0600 (CST) From: Mumit Khan To: Josifovski Ljubomir-BLJ01Z cc: "Cygwin Mailing List (E-mail)" Subject: Re: [OT] #!/usr/bin/env bash -vx In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 31 Jan 2001, Josifovski Ljubomir-BLJ01Z wrote: > > This is not exclusive to cygwin, but maybe someone here can help me. I put > > #!/usr/bin/env bash > > in the first line on some scripts I use on Cygwin, Linux and HP-UX because > the exact path to bash differs (someone posted this trick on the list > sometime ago). But when arguments are added to the line, like > > #!/usr/bin/env bash -vx > > this doesn't work anymore - I get: It's the way env works, especially in conjunction with '#!'. If you really want to do this, create a wrapper script, where you can define all the flags. In this example, the interpreter Cygwin or Linux or any other OS will call up is "bash -vx", which is it not a valid interpreter name ("bash" by itself is of course). Regards, Mumit -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple