Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: PATCH: new _print and thoughts on _arguments mutexes

X-seq: zsh-workers 10842
From: Zefram <zefram@xxxxxxxx>
To: Oliver Kiddle <opk@xxxxxxxxxxxxx>
Subject: Re: PATCH: new _print and thoughts on _arguments mutexes
Date: Wed, 19 Apr 2000 16:13:20 +0100 (BST)
Cc: Zsh workers <zsh-workers@xxxxxxxxxxxxxx>
In-reply-to: <38FDC509.C00E9709@xxxxxxxxxxxxx> from Oliver Kiddle at "Apr 19, 2000 03:39:05 pm"
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm

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/<foo>/fd/<n> is scarily useful.

-zefram

Follow-Ups:
- Re: PATCH: new _print and thoughts on _arguments mutexes
  - From: Oliver Kiddle

References:
- PATCH: new _print and thoughts on _arguments mutexes
  - From: Oliver Kiddle

Messages sorted by: Reverse Date, Date, Thread, Author