From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12903 invoked from network); 30 May 2000 08:17:00 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 30 May 2000 08:17:00 -0000 Received: (qmail 12009 invoked by alias); 30 May 2000 08:16:51 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11651 Received: (qmail 12002 invoked from network); 30 May 2000 08:16:51 -0000 Date: Tue, 30 May 2000 10:16:47 +0200 (MET DST) Message-Id: <200005300816.KAA19770@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Tue, 30 May 2000 07:54:31 +0000 Subject: Re: #compdef tag and menu-select Bart Schaefer wrote: > If one has already loaded the complist module before running compinit, then > one can use `#compdef -k menu-select ...' at the top of completion functions. > > If one has not already loaded complist, then compdef chokes. > > At other places in the completion system we automatically load complist when > it seems wanted. Perhaps compdef should too? If I had thought of it, I probably would have done that. Nowadays I'm a bit reluctant to change that because I've too often thought about removing menu-select -- after all, it's just menu-complete with enforcing selection, which can be achieved by other means. And there is the question if menu-select should be re-bound to _main_complete when compdef finds a widget using menu-select. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de