From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13683 invoked from network); 3 Apr 2000 08:39:48 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 Apr 2000 08:39:48 -0000 Received: (qmail 8519 invoked by alias); 3 Apr 2000 08:39:33 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10400 Received: (qmail 8512 invoked from network); 3 Apr 2000 08:39:32 -0000 Date: Mon, 3 Apr 2000 10:39:31 +0200 (MET DST) Message-Id: <200004030839.KAA13283@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Mon, 3 Apr 2000 01:29:59 +0000 Subject: Re: zrecompile Bart Schaefer wrote: > On Apr 2, 2:01pm, Andrej Borsenkow wrote: > } Subject: zrecompile > } > } This is the second time ... not sure what's going wrong: > } > } bor@itsrm2% zrecompile > } zrecompile:zcompile:144: invalid dump file: > } /home/bor/.zsh.d/completion.zwc > > I get that error when I try to use -dev-20 to recompile a file that was > written with -dev-19. I think the -k/-z option changes introduced this > incompatibility. You'll just have to recompile "by hand." Right. zrecompile should be a bit more clever to handle error conditions, though. And another thing: the zwc files till use $ZSH_VERSION in the header to test for compatibility -- somehow I didn't like to add an additional version number scheme for them, but it would be better, I think (the format will certainly change less often than $ZSH_VERSION). No patch, I'm still compiling the thing from CVS... Bye Sven P.S.: Sourceforge Bug #103797 can be closed, it seems. It also seems that only administrators can do that. -- Sven Wischnowsky wischnow@informatik.hu-berlin.de