From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6793 invoked from network); 19 Apr 2000 15:14:23 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Apr 2000 15:14:23 -0000 Received: (qmail 15426 invoked by alias); 19 Apr 2000 15:13:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10842 Received: (qmail 15412 invoked from network); 19 Apr 2000 15:13:38 -0000 Subject: Re: PATCH: new _print and thoughts on _arguments mutexes In-Reply-To: <38FDC509.C00E9709@u.genie.co.uk> from Oliver Kiddle at "Apr 19, 2000 03:39:05 pm" To: Oliver Kiddle Date: Wed, 19 Apr 2000 16:13:20 +0100 (BST) CC: Zsh workers X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Zefram Oliver Kiddle wrote: > Does anyone know how I can determine if there is a >currently active coprocess so the -p flag is only offered if it can be >used. I suppose you could play with (:>&p) type stuff. > I can find out which file-descriptors are currently active using >/dev/fd/n tests but I haven't bothered because it wouldn't be much use >unless I could create meaningful descriptions of the file/pipe that the >file-descriptor points to. Under Linux, readlink(2) on /proc//fd/ is scarily useful. -zefram