Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: #compdef -k menu-select glitch in 3.1.9
- X-seq: zsh-workers 11765
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: #compdef -k menu-select glitch in 3.1.9
- Date: Tue, 6 Jun 2000 05:16:26 +0000
- In-reply-to: <1000606045656.ZM65@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <1000606045656.ZM65@xxxxxxxxxxxxxxxxxxxxxxx>
On Jun 6, 4:56am, Bart Schaefer wrote:
} Subject: #compdef -k menu-select glitch in 3.1.9
}
} If I explicitly invoke `zle -C _widget .menu-select _widget' then I do get
} menu-select behavior, but for some reason it doesn't work at compinit time.
I found out what's happening: this is partly pilot error on my part, and
partly bad behavior from compinit.
I have two files in my $fpath both named _widget with different #compdef
tags. compinit processes both of them, in $fpath order, which means that
the #compdef that wins doesn't match the function that gets autoloaded. I
expected it to only process the one that would actually be autoloaded.
Should we stick a `(( $+functions[$_i_file] )) && continue' or equivalent
into the `for _i_file in ...' loop in compinit?
The other puzzler, with the beeping, still remains.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author