From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17848 invoked by alias); 17 Sep 2015 23:06:31 -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: 20577 Received: (qmail 170 invoked from network); 17 Sep 2015 23:06:29 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Authority-Analysis: v=2.1 cv=X+5rdgje c=1 sm=1 tr=0 a=zebyiQhrbmDl3XZzCDMMUg==:117 a=zebyiQhrbmDl3XZzCDMMUg==:17 a=N659UExz7-8A:10 a=66NBXdpU72xp7p3x9OAA:9 a=pILNOxqGKmIA:10 Message-id: <55FB476F.7080106@eastlink.ca> Date: Thu, 17 Sep 2015 16:06:23 -0700 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-version: 1.0 To: zsh-users@zsh.org Subject: Re: autoload References: <55FAE223.2080502@eastlink.ca> <150917103419.ZM10067@torch.brasslantern.com> <55FB12FD.8000504@eastlink.ca> <150917134047.ZM10250@torch.brasslantern.com> In-reply-to: <150917134047.ZM10250@torch.brasslantern.com> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 09/17/2015 01:40 PM, Bart Schaefer wrote: > Yes, and the problem is that you've put .zwc files into the directories > in that hardcoded list, but then tried to use the hardcoded list to > (re)build yet another .zwc file. But I didn't create those files. They're dated August 31 which seems to be common to most of the files in the distro as I downloaded it. Is this something to do with Debian? > I'm not really sure how further to explain this. The sample code that > I provided takes EVERY DIRECTORY that's in (the default) $fpath and > packs ALL the files under them into ONE .zwc. That's how I read it. You on the other hand seem to have already built a separate .zwc out of EACH directory of the default $fpath. If you're using my example, you don't need to do that - you should throw all those .zwc away and use the single one that my sample builds. I tried deleting all of them which resulted in ~/.zsh-default-functions.zwc being created, but zero length and of course nothing worked. With original .zshrc code, things worked but a 'time' test was very slow, thus demonstrating the effectiveness of the .zwc idea itself (by it's absence, in this case). I restored the .zwc files and I'm back to normal. This seems to be a very tricky business. Perhaps not worth wasting your time on. It seems a shame that zcompile doesn't know not to trip over itself, one might expect to find a .zwc file in the same dir as the files from which it was built. Or not. > } zcompile $zsh_default_functions $^fpath/*(N.:t) << 't' being a > } new friend > > } A different enemy, more like. > Sure, it was just experiment, I hardly expected it to be correct.