behaviour of "for (( exp1; exp2; exp3 )); do COMMANDS; done"

[Stuart Brady]

On Tue, May 27, 2003 at 10:45:50AM +0200, Peter Oosterlynck wrote:

> My workaround: added "#!/usr/bin/bash" in my cygwin script.

I'm not sure that this isn't the correct approach in the first place.
Of course, bash isn't always going to be /usr/bin/bash, so maybe you
really want "#!/usr/bin/env bash" or something. Either way, you
shouldn't be suprised to see bash or tcsh-specific shell scripts
rejected by whatever your /bin/sh happens to be. This will most likely
affect Solaris, HP-UX, FreeBSD and many others. It also affect Linux if
your distribution's /bin/sh isn't what you expected it to be.
-- 
Stuart Brady

--
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/