X-Spam-Check-By: sourceware.org From: "Dave Korn" To: "'cygwin'" Subject: RE: Help running bash scripts Date: Wed, 22 Nov 2006 12:27:14 -0000 Message-ID: <023001c70e31$8ac178b0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <001301c70df6$77e7e2f0$0a00a8c0@s3000p> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 22 November 2006 05:24, David Christensen wrote: > Thierry wrote: >> running a simple sh script(test.sh): >> #!/bin/sh >> # test > >> $ ./test.sh >>> command not found > > Get this book: > > http://www.oreilly.com/catalog/bash3/index.html > > > "test" is a Bash built-in command ("man bash"; see CONDITIONAL > EXPRESSIONS). Avoid using that keyword in Bash scripts and anywhere > else Bash might trip over it (such as script and program names). "test" != "test.sh". No confusion is at all possible. Bash is not DOS and does not attempt to append .exe/.com/.bat extensions to every command filename entered, and nor does it try appending .sh either. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/