zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: zrecompile
Date: Mon, 3 Apr 2000 10:39:31 +0200 (MET DST)	[thread overview]
Message-ID: <200004030839.KAA13283@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 3 Apr 2000 01:29:59 +0000


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


             reply	other threads:[~2000-04-03  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-03  8:39 Sven Wischnowsky [this message]
2000-04-03  9:45 ` zrecompile Sven Wischnowsky
2000-04-03 10:01   ` zrecompile Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2000-04-02 10:01 zrecompile Andrej Borsenkow
2000-04-03  1:29 ` zrecompile Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200004030839.KAA13283@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).