Great. Have you tested whether the -e flag gets propagated inside the
functions?
Yes, I have now:
$ /bin/sh -e ; echo finished /bin/sh -e, status=$?
$ echo $-
eims
$ # the -e flag propagates into subshells:
$ tst1() { echo $- ; }
$ tst1
eims
$ # false result inside a function
teTeX 2.99.1 can be considered something of a release candidate.
I've made considerable efforts to make teTeX 3.0 [cross] build out of
the box for Cygwin, many thanks to Thomas Esser and Olaf Weber.
This release has major changes since 2.0.2, so I do not think
it's wise to put this in the test
On Fri, Oct 29, 2004 at 11:11:17AM -0700, Dave wrote:
The logic required is:
If the environment variable CHERE_INVOKING is present, do not change to
the users home directory.
http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/base-files-3.1-2.tar.bz2
Sorry, the above is wrong:
Sorry again, but please disregard my previous message. I was confused
because I was testing some features of /bin/sh -e on Debian. On Debian
/bin/sh invokes bash, while on Cygwin it runs ash. It turns out that these
two handle subshells with -e differently:
