From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-workers-request@euclid.skiles.gatech.edu Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by coral.primenet.com.au (8.7.5/8.7.3) with ESMTP id IAA10152 for ; Wed, 30 Oct 1996 08:49:39 +1100 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id QAA18173; Tue, 29 Oct 1996 16:51:09 -0500 (EST) Resent-Date: Tue, 29 Oct 1996 16:39:58 -0500 (EST) From: Zefram Message-Id: <10786.199610292139@stone.dcs.warwick.ac.uk> Subject: Re: pipes and redirection To: gsker@lenti.med.umn.edu Date: Tue, 29 Oct 1996 21:39:51 +0000 (GMT) Cc: zsh-users@math.gatech.edu In-Reply-To: from "Gerald Skerbitz" at Oct 29, 96 01:22:23 pm X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]8344.51 X-US-Congress: Moronic fuckers Content-Type: text Resent-Message-ID: <"u2dIZ2.0.TN4.kcdTo"@euclid> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/473 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >The goal is to get stdout to go to a file, and stderr to be piped to >another program. (print -u2 This is stderr;print This is stdout) 1>test 2>>(tr a-z A-Z > test2) Unfortunately the command inside >() gets executed asynchronously, but that suffices in many cases. (Out of interest, why is it asynchronous? I've always thought that synchronous execution, as with normal pipelines, would be more natural and usually more useful.) -zefram