From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8180 invoked from network); 29 Jun 1999 11:47:42 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 29 Jun 1999 11:47:42 -0000 Received: (qmail 18621 invoked by alias); 29 Jun 1999 11:47:34 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6916 Received: (qmail 18614 invoked from network); 29 Jun 1999 11:47:34 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: "ZSH workers mailing list" Subject: compinit/compdef useful outside of completion? Date: Tue, 29 Jun 1999 15:47:25 +0400 Message-ID: <001101bec225$27f21e70$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Don't you think, that these can be used not only with completion widgets? I actually like the idea, when I just need to drop a file in defined place and it will automatically be used next time I start shell. No more .zshrc editing etc. What I mean, does it make sense to extend compinit/compdef to handle "normal" user defined widgets as well ('course, the names will probably be too misleading ...). E.g. 'compdef -w widget function' to define normal widget. You could even automatically bind it to key sequence with additional parameter ... say "-k ^Xn"? And start function with '#compdef -w ' Comments? /andrej