From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18655 invoked from network); 21 Jan 2009 17:12:03 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.2.5 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 21 Jan 2009 17:12:03 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 9315 invoked from network); 21 Jan 2009 17:11:58 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 21 Jan 2009 17:11:58 -0000 Received: (qmail 3050 invoked by alias); 21 Jan 2009 17:11:54 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 26396 Received: (qmail 3040 invoked from network); 21 Jan 2009 17:11:54 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 21 Jan 2009 17:11:54 -0000 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by bifrost.dotsrc.org (Postfix) with ESMTP id D41E2802720F for ; Wed, 21 Jan 2009 18:11:49 +0100 (CET) Received: by fg-out-1718.google.com with SMTP id e21so1716422fga.37 for ; Wed, 21 Jan 2009 09:11:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=BNzN4oUuehQbbcdBBFUQ8LLjhWB4UAAZheAPA3QK4/w=; b=DIB54f9OMDyG/hf+4gaOv76OS9BRjByFzkvg/E3pr8m1jwZIATbTlYWhLlEE0CKRSN 4rC6ZPMcwHV/B8nEPRycmMH5bLybJqNYRRRCtmzhAaxTlWmAsZApz8JDhPI20WBnQCX0 UiXh2PRwDbTOl8NAKgxywj9plfLAgtozgB61M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=cAsel68R5PZdnjGXoQNGWVN2nkLPrBs4Thju5HPt9lkAb/anCiF7fIlRaMQCmOppgy AN+TRE1r1HMOPmde9hKS3077j0z5XtCXvdjujtqTi1wcQ5zz50uwGAeM4ow1aQeTkw0f CvucPy4Kzp1lRbRl6kLCGSsI7YmA+CojRpixg= MIME-Version: 1.0 Received: by 10.86.94.11 with SMTP id r11mr609609fgb.53.1232557909454; Wed, 21 Jan 2009 09:11:49 -0800 (PST) In-Reply-To: <2d460de70901100115x129a6405md5ca6ca8d1629c5c@mail.gmail.com> References: <2d460de70901100115x129a6405md5ca6ca8d1629c5c@mail.gmail.com> Date: Wed, 21 Jan 2009 18:11:49 +0100 Message-ID: <2d460de70901210911p1e29b7dkb4727ed14227836d@mail.gmail.com> Subject: Re: Convention question regarding completions From: Richard Hartmann To: "Zsh Hackers' List" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.92.1/8884/Wed Jan 21 14:15:32 2009 on bifrost X-Virus-Status: Clean Bump. On Sat, Jan 10, 2009 at 10:15, Richard Hartmann wrote: > Hi all, > > when writing completions, should I XAND only the options > which are really mutually exclusive like > > tar x > tar c > > or should I XAND the ones which won't work but won't hurt, > either like > > --verbose > --quiet > > or should I XAND even the ones which become superfluous > like the second option in > > deluser --remove-all-files > deluser --remove-home > > ? > > Personally, I lean towards the third, i.e. most inclusive > XAND rule, but I am interested what the others think. > > > Richard > > PS: Just in case it's not clear from context what I mean > by XAND: > > '(x)c[create a new archive]' > '(c)x[extract files from an archive]' >