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" <[EMAIL PROTECTED]> > 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/
