X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
Message-ID:	<4D065560.9060301@redhat.com>
Date:	Mon, 13 Dec 2010 10:18:24 -0700
From:	Eric Blake <eblake AT redhat DOT com>
User-Agent:	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.7
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Executable named "[.exe" in c:\cygwin\bin?
References:	<AANLkTiktvSMLdZ_1+oDGg9kOVHbhRAX7K_s+c72mUDQe AT mail DOT gmail DOT com> <AANLkTimtxEVwMF-bDWot2OO7pGZ7uz1K5hQEw+H9efPX AT mail DOT gmail DOT com> <4D04C14E DOT 90607 AT gmx DOT de> <4D04C262 DOT 50507 AT gmail DOT com> <4D04D130 DOT 9090006 AT gmx DOT de> <20101212195154 DOT GG14369 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To:	<20101212195154.GG14369@ednor.casa.cgf.cx>
OpenPGP:	url=http://people.redhat.com/eblake/eblake.gpg
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

--------------enig6EACBD1C43D24E28912FF49C
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 12/12/2010 12:51 PM, Christopher Faylor wrote:
>>>     `-e'
>>>           Exit immediately if a simple command (*note Simple
>>>           Commands::) exits with a non-zero status, unless the command
>>>           that fails is part of the command list immediately following
>>>           a `while' or `until' keyword, part of the test in an `if'
>>>           statement, part of a `&&' or `||' list, or if the command's
>>>                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>           return status is being inverted using `!'.  A trap on `ERR',
>>>           if set, is executed before the shell exits.
>>>
>>
>> Yes, in theory.  In practice, I've seen too many shells goof this up.
>=20
> Maybe in 1986 there was a shell which didn't do this properly under Ultri=
x.
> I sincerely doubt that any modern shell has a problem.

Then you seriously underestimate the non-portability of 'set -e', even
between different versions of bash.  When the POSIX specification for
'set -e' had to be changed yet again just this year to try and tighten
down all the subtleties, it's no wonder that shells vary widely in its
implementation.

http://www.gnu.org/software/autoconf/manual/autoconf.html#index-g_t_0040com=
mand_007bset_007d-1719

http://austingroupbugs.net/view.php?id=3D52

--=20
Eric Blake   eblake AT redhat DOT com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org


--------------enig6EACBD1C43D24E28912FF49C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJNBlVgAAoJEKeha0olJ0NqGqQH/imNcpUIflUpUqzBSPnjOdGi
jqTTOTiVKCj70Q2/O48IzdKeZPYFSTBqqQPGWNiCwnvYBdBGFZfWJ0vP8Mnx1m85
e0qcC8h2yS2XPuJaImu+kr4ITT41VGf0IcVTg6fPKaBRPJbT78j8HHOuJw5NrXNl
2oaXdru66uWepqnBBUKwreZ5TurLtwGN8UWJYIcKD/qR6KP90zDVQ2Hg2W49uctK
RWy4Mv69iBjbVzDMp4T+AKAWrsPTHQRZd/PooYgx0aTt56esGUGI/f3UJ8bg3xu7
+1o6RVbZX/8DGgtDmKBmrp9AHvSSzxkU2bT0SPZfUn5cRTX36PuJTbZWOXzMR38=
=Q/+l
-----END PGP SIGNATURE-----

--------------enig6EACBD1C43D24E28912FF49C--

- Raw text -