From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19649 invoked by alias); 23 Jul 2014 03:58:46 -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: 32894 Received: (qmail 14804 invoked from network); 23 Jul 2014 03:58:33 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) 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 autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140722205805.ZM23154@torch.brasslantern.com> Date: Tue, 22 Jul 2014 20:58:05 -0700 In-reply-to: <18723.1406025098@thecus.kiddle.eu> Comments: In reply to Oliver Kiddle "using tag-order with _pids" (Jul 22, 12:31pm) References: <18723.1406025098@thecus.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh workers Subject: Re: using tag-order with _pids MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Jul 22, 12:31pm, Oliver Kiddle wrote: } Subject: using tag-order with _pids } } The patch below moves the use of _call_program by _pids to inside the } _tags loop. So ... before, there was no _tags loop at all. } Much of the patch is just reindentation. The purpose of this } is to allow separate processes to be grouped so _next_tags can expand } the list to include a wider range of processes. Maybe another way to do this is to keep a single _call_program outside the new _tags loop, and use a new zstyle inside the loop to partition the "ps" output by pattern matching? Since _pids is already "parsing" the ps header line to figure out what column the actual PID is in, the style could potentially specify that the pattern had to match in a particular column.