Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: problems with #compdef

X-seq: zsh-workers 15644
From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
To: zsh-workers@xxxxxxxxxx
Subject: Re: problems with #compdef
Date: Thu, 16 Aug 2001 15:06:25 +0200
In-reply-to: <20010816135151.B20118@xxxxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20010815161518.A14385@xxxxxxxxxxxxxxxxxxxxxxx> <1010815161937.ZM10338@xxxxxxxxxxxxxxxxxxxxxxx> <20010816135151.B20118@xxxxxxxxxxxxxxxxxxxxxxx>

Adam Spiers wrote:

> ...
> 
> Well I ran compdump, which I thought was equivalent, but evidently
> not, because removing it does indeed work.  Thanks a lot.  So why
> isn't compdump sufficient?

Because compdump only dumps the current state, it doesn't re-examine
the files.  This is so that one can change things by executing compdef 
commands on the command line and then call compdump without having
that overwritten by compdump preferring the things in the files.

Bye
  Sven

-- 
Sven Wischnowsky                    wischnow@xxxxxxxxxxxxxxxxxxxxxxx

Messages sorted by: Reverse Date, Date, Thread, Author