From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 323 invoked by alias); 28 Jan 2017 18:09:17 -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: 40438 Received: (qmail 27417 invoked from network); 28 Jan 2017 18:09:17 -0000 X-Qmail-Scanner-Diagnostics: from mercury.zanshin.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(64.84.47.142):SA:0(-0.0/5.0):. Processed in 1.049024 secs); 28 Jan 2017 18:09:17 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at ipost.com designates 64.84.47.142 as permitted sender) Date: Sat, 28 Jan 2017 10:08:42 -0800 (PST) From: Bart Schaefer Reply-To: Bart Schaefer To: Zhiming Wang cc: Zsh hackers list Subject: Re: Completion of swift fails when swift(1) is from Apple, not OpenStack In-Reply-To: <9787F242-39F4-4151-85A1-3F6A109A9FB1@princeton.edu> Message-ID: References: <9787F242-39F4-4151-85A1-3F6A109A9FB1@princeton.edu> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) X-Face: "f/X=UCVgd*^c>+x(gMq0at?e:woX+;'snkkRzc3SX<0AZ (/PS4.M2hzGS9X:Qj]at_H/%a9K}:-eS<"v_7vX84PG9Bf Zpb`wI!I4geY=or+nWq`3CX`oq&TJR;g^ps|7(MH?jh;bs %vHJfCh5>a*6Re5m|Bidja\\o]>n\A)ib1:yX*T`zR(*h~ %tOw<~!D9{e6h!8M2:d8G2@K>y^1I_Vdy\d\MYe]z7c MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 28 Jan 2017, Zhiming Wang wrote: > Now that the conflict is obvious, I wonder what's the best course of > action. Probably the right thing is to add _swift, and use _pick_variant to choose whether to call _openstack or to complete Apple's compiler options.