Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <006a01c35cc9$9c0522b0$2564a8c0@blackmagic> From: "sandeep" To: "Andrew Markebo" Cc: References: <001c01c35cbe$cbbc9020$2564a8c0@blackmagic><003401c35cc0$8bc781d0$2564a8c0@blackmagic> Subject: Re: (latest install from site) cygwin1.dll 1.3.22-dontuse-21 --bashbuggy behaviours under windows 2000 Date: Thu, 7 Aug 2003 15:22:27 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Thanks Andrew for the tip. I have been using set -x .... section of script that needs debugging ... set +x to specifically examine how bash is treating it. This way the less but relevant is available for examination. ----- Original Message ----- From: "Andrew Markebo" > OK hmm no idea.. meanwhile, you know that you can throw parameter "-v" > on the shell starting the script and then you can see how the script > expands/replaces stuff and so on. > > Like: > > bash -v scriptname > or > #!/bin/bash -v > > in the script --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.507 / Virus Database: 304 - Release Date: 8/4/2003 -- 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/