From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 465 invoked by alias); 26 Jun 2015 14:19:41 -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: 35614 Received: (qmail 28681 invoked from network); 26 Jun 2015 14:19:39 -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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 Message-ID: <558D5E34.3020505@inlv.org> Date: Fri, 26 Jun 2015 16:14:12 +0200 From: Martijn Dekker User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Bart Schaefer , zsh-workers@zsh.org Subject: Re: '>>' does not create file if set -C (noclobber) is active References: <558B5342.2090706@inlv.org> <150624184916.ZM19079@torch.brasslantern.com> <558B65EB.3060204@inlv.org> <150625003047.ZM19218@torch.brasslantern.com> In-Reply-To: <150625003047.ZM19218@torch.brasslantern.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Bart Schaefer schreef op 25-06-15 om 09:30: > So I'm still inclined to say that this > is just not going to change, because we'd either have to (1) change it in > native mode or (2) do one of those hacks that tests the emulation mode > so it only works if you actually start the shell that way or (3) add an > entirely new setopt just for this. I don't like any of those choices. I can understand and sympathize with this point of view. But, from my point of view as someone writing cross-platform POSIX shell programs, this is a legitimate compliance bug that breaks scripts running under 'set -C' that should be expected to work according to the standard. (It has done in at least one real-life case, i.e. mine). A shell-specific 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. So I hope you're willing to reconsider and think of a solution -- perhaps a SH_APPEND shell option (which would also apply to ksh emulation). Thanks, - M.