From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4118 invoked by alias); 26 Jun 2015 20:15:30 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35619 Received: (qmail 28791 invoked from network); 26 Jun 2015 20:15:28 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=LmMwKwb0wdzd3zC66ped/B1ewz3CK820I2fqkxuuKDw=; b=KOGij9879nqB1XMDZzy8hZApSVwe/XfSbQoAmA6itxL+TGJHutCMg1j4HgKmEjYOYS cpS+6lbQc/r7QibNeFaLP//ugytUPxe07+qcxZDp5tWhMeYKPSrlhADbE7Uk16HTuFeS JFqwa6rD/9Kcabu6Giix0h0zMwIWo36HzvWOmM/vteEGYkIRxggVVksm72O1CQPiWOJS Lb/NgEZbrkMvSWJP0KFeeV6DcBfe6fV8Z61TCtdEWr27o1u+y1s4ozItvnmQ/xuA7bOt YcNkgIoMZI7qHAFjaKci63TdRv6q/QNZ8ljYL+4fSVpR/OOBN69ZlsZnYZlsAz+cCxq7 pNQQ== X-Gm-Message-State: ALoCoQmWOAe2xuUEp0igUCFtr1EspLv1kf5YNVcG5PdmNHUU94S2excLozaWvVmNJipv7RuVDR/K X-Received: by 10.202.93.4 with SMTP id r4mr2969246oib.92.1435349725737; Fri, 26 Jun 2015 13:15:25 -0700 (PDT) From: Bart Schaefer Message-Id: <150626131522.ZM21498@torch.brasslantern.com> Date: Fri, 26 Jun 2015 13:15:22 -0700 In-Reply-To: <558D5E34.3020505@inlv.org> Comments: In reply to Martijn Dekker "Re: '>>' does not create file if set -C (noclobber) is active" (Jun 26, 4:14pm) References: <558B5342.2090706@inlv.org> <150624184916.ZM19079@torch.brasslantern.com> <558B65EB.3060204@inlv.org> <150625003047.ZM19218@torch.brasslantern.com> <558D5E34.3020505@inlv.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: '>>' does not create file if set -C (noclobber) is active MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 26, 4:14pm, Martijn Dekker wrote: } } workaround ought not to be necessary for this. If the goal of 'emulate } sh' is to provide a compatible POSIX environment then this situation is } clearly inconsistent with that goal. The goal of "emulate sh" is to provide a Bourne-sh compatible environment, for the most part. Just for example, neither POSIX_ARGZERO nor POSIX_CD is turned on by default in any of the "emulate" modes, and there are a number of other POSIX-isms that are not (yet, at least) supported at all. That said, I'm not trying to shut down discussion of this issue, I'm just pointing out that we're going to be choosing a least of evils whether we do something or do nothing.