From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18885 invoked from network); 11 Jan 2000 17:41:55 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 11 Jan 2000 17:41:55 -0000 Received: (qmail 24031 invoked by alias); 11 Jan 2000 17:41:42 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2860 Received: (qmail 24022 invoked from network); 11 Jan 2000 17:41:41 -0000 From: "Bart Schaefer" Message-Id: <1000111174118.ZM9719@candle.brasslantern.com> Date: Tue, 11 Jan 2000 17:41:18 +0000 In-Reply-To: <20000110195717.A1119@tdc100.comm.mot.com> Comments: In reply to Paul Ackersviller "clobbering with >&" (Jan 10, 7:57pm) References: <20000110195717.A1119@tdc100.comm.mot.com> X-Mailer: Z-Mail (5.0.0 30July97) To: Paul Ackersviller , zsh-users@sunsite.auc.dk Subject: Re: clobbering with >& MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jan 10, 7:57pm, Paul Ackersviller wrote: } Subject: clobbering with >& } } Here's something I don't see covered in the docs -- is it possible to } override the noclobber variable when doing output redirection with >&? } I've tried the obvious permutations of ! and | with it, but just get syntax } errors. What syntax errors? Can you give a precise example, please? } Never mind, I just answered my own question. It appears >&\! will do the } trick. Perhaps this should be documented. Both >&| and >&! *should* work just fine, without the backslash. Note that you need a space after the `!' to prevent it being from taken as a history reference, but even that isn't necessary with the `>&|' form. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com