From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4576 invoked by alias); 15 Mar 2012 07:31:52 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 16888 Received: (qmail 13116 invoked from network); 15 Mar 2012 07:31:49 -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.6 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_LOW, T_DKIM_INVALID autolearn=no version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.213.43 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FRNA67KgMemrArO5Bz5IFTFgW+27+R81aGysO9rf5j4=; b=e2NobO9/Iyurs3W/QbLkpGvpJrt58L3iak29CWAt2TnIc+rECFvurw2FMJHmv59cac uq4TlD5Yjtj7J9GYbUnimXf0bH3h96xlcqDIF4udzvEgit7Y3w3K2uU1jbrK7Vaf+BmV SoXYKo6RVuvOuTY41t8Pq4blS5m1UkHrGNzsrid6hOTjrjDR2Oj3ieGn9Afv1IrKqo+X MYiJsgT5rpD4sRaWn713Q+XZayt8QxUcHj+4Da9HNKjtuwaNk3Xm3lsYTy8d30c1frVD upC8e2d9J2fSnfW1uMUHkN8d8tYnCHb4liyM4ocxL4tF47WZZmNPUNO80bKvKZDORER7 /ecA== MIME-Version: 1.0 In-Reply-To: <120314101917.ZM25639@torch.brasslantern.com> References: <120314101917.ZM25639@torch.brasslantern.com> Date: Thu, 15 Mar 2012 08:31:44 +0100 Message-ID: Subject: Re: Putting options after tasks From: =?ISO-8859-1?Q?Jesper_Nyg=E5rds?= To: Bart Schaefer Cc: zsh-users@zsh.org Content-Type: text/plain; charset=ISO-8859-1 On Wed, Mar 14, 2012 at 6:19 PM, Bart Schaefer wrote: > _arguments is designed to assume that programs accept all options first > and all other arguments after them. Naive question: why? It seems to be a great deal of programs can take their options at any position nowadays. > Given that the tasks and options can be freely mixed in this way, I > presume that none of the options take a following argument (that is, > "--foobar zoom" never means that "zoom" must appear immediately after > "--foobar"). No, unfortunately that's not true, only my simplified example gave that impression. In reality, some of the options can take a following argument. > If that's true, then one possibility... Thank you very much for this, Bart. Since Mikael has reported that it seems to work going down the _arguments route, I'll have a go at that, and see if it works also when I expand my example to the real set of options. I'll report back if I run into trouble.