X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sun, 12 Dec 2010 14:51:54 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Executable named "[.exe" in c:\cygwin\bin? Message-ID: <20101212195154.GG14369@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4D04C14E.90607@gmx.de> <4D04C262.50507@gmail.com> <4D04D130.9090006@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D04D130.9090006@gmx.de> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sun, Dec 12, 2010 at 02:42:08PM +0100, Matthias Andree wrote: >Am 12.12.2010 13:38, schrieb Daniel Colascione: >> On 12/12/10 4:34 AM, Matthias Andree wrote: >>>> [ -f file ] && echo is >>> you cannot run scripts containing this >>> under a "set -e" regime. >> >> Yes you can. >> >> `-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. Maybe in 1986 there was a shell which didn't do this properly under Ultrix. I sincerely doubt that any modern shell has a problem. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple