From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id e7165656 for ; Tue, 18 Dec 2018 00:22:35 +0000 (UTC) Received: (qmail 5703 invoked by alias); 18 Dec 2018 00:22:22 -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: List-Unsubscribe: X-Seq: 43910 Received: (qmail 27145 invoked by uid 1010); 18 Dec 2018 00:22:22 -0000 X-Qmail-Scanner-Diagnostics: from out1-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.100.2/25112. spamassassin: 3.4.2. Clear:RC:0(66.111.4.25):SA:0(-2.6/5.0):. Processed in 2.844589 secs); 18 Dec 2018 00:22:22 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= daniel.shahaf.name; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:references:date :in-reply-to; s=fm2; bh=qm+BC4gyV7srnnYNcc2Lrq4aZtPMNuxs+PimwOIF vcU=; b=bkRU6kMZmCrt5qeDDw7IXHWVmTAiixziGMEpD+Nu44KT8cd4Wqsp1fuM XdS4sR1gJ7S2Dat7NP8hFUMAMHUULIj4xUm4wnP9S5l4hpO3+rMCyjQclENKbV9R NMY/tFSedTDM5JQGJSCUZmlnkhas6bNShPm/3mKTUmhtu/LPOUf3HcRwv7RSrFkp dT/lD2rHFWxPPRbFnox0I6Xif/BY5a6BJxMpbKJ40RVyUz0W3LZhTBrAG5rimFO5 Nr5/+ccV8C6RfHQTXvH/ZIoj4F/5kUV5RL37hthKjJSZjMbck/sz7H6TSTsO1soE ywbCdoet/FdBkHAj2Cxk4VUs/hNOyA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=qm+BC4gyV7srnnYNcc2Lrq4aZtPMNuxs+PimwOIFv cU=; b=FdWV7G2rBYfxOp29lpHyzbwOtm54Uf5MGMJBQu/n7k+W7FSAV9rqqP1Mp FhAJJUrkosyWUt2kzgCk7bz4XWZ/vrAyZtYF44G/F4ukPavRDzYWdZB6GwcnKmw9 7aF0D4Y2KegDomuPQEE9Mh3RS5S6sGt/l8RR43hy7DN8t9EACFZIXhUYN0HciljV UaC7Fs8ZHjOpY7fcyiXIw6sa55Jo7DDgSdhvgSWcm5NHLIXcjU5oBLm8DCdEz+YO 2bOFOauMCRHvWXRSXZyVMmDvzxivaXESjVXFdqsV5TYUbi0LdWxH72PfJApZ+z1b 52i6hqPNckgCJzYaTdNIn3h1K8OfQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudeigedgvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecunecujfgurhepkffhvfgggfgtoffufhffjgesthejredtredtjeenucfhrhhomh epffgrnhhivghlucfuhhgrhhgrfhcuoegurdhssegurghnihgvlhdrshhhrghhrghfrdhn rghmvgeqnecurfgrrhgrmhepmhgrihhlfhhrohhmpegurdhssegurghnihgvlhdrshhhrg hhrghfrdhnrghmvgenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Message-Id: <1545092536.601174.1611972136.2F0901D0@webmail.messagingengine.com> From: Daniel Shahaf To: zsh-workers@zsh.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-2f590f9a Subject: Re: [PATCH/RFC] Completion: Add _composer References: <6D1B6E3C-52B9-4AB6-BC48-3C279FCF33FC@dana.is> <1545092371.600233.1611967824.063830D4@webmail.messagingengine.com> Date: Tue, 18 Dec 2018 00:22:16 +0000 In-Reply-To: <1545092371.600233.1611967824.063830D4@webmail.messagingengine.com> Daniel Shahaf wrote on Tue, 18 Dec 2018 00:19 +0000: > dana wrote on Mon, 17 Dec 2018 17:09 -0600: > > * Perhaps most questionable is __composer_packages. I couldn't figure out how > > to reliably complete arbitrary package names, because Composer is incredibly > > slow to return them, and there are so many that it didn't perform much better > > when i tried the usual array-caching mechanism. Even asking Composer about > > packages listed in the project JSON files is pretty slow, and not always > > accurate. To work around those problems i 'seeded' the function with a bunch > > of the most popular packages, and then i used `grep -o` to 'parse' the names > > out of the JSON files. Hard-coding package names in feels especially weird, > > but...? > > Are you familiar with _store_cache and cache-policy? It's not clear > from the comments > whether you've tried that. (And sorry for the fullquote. I thought I'd trimmed it.)