From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9068 invoked from network); 7 Jul 1999 08:13:57 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 7 Jul 1999 08:13:57 -0000 Received: (qmail 350 invoked by alias); 7 Jul 1999 08:13:43 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6994 Received: (qmail 341 invoked from network); 7 Jul 1999 08:13:43 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: "Sven Wischnowsky" , Subject: RE: PATCH: more fun with `zle' Date: Wed, 7 Jul 1999 12:13:28 +0400 Message-ID: <000401bec850$983101c0$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) In-Reply-To: <199907070751.JAA09744@beta.informatik.hu-berlin.de> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 > > And: all of this is only a suggestion for things that may be > interesting to have. I'm not really happy with the argument-parsing > and -naming of `zle' (and I never really understood why we have to > have the concept of a widget -- maybe a special builtin/shell > function-type would be more appropriate nowadays; but that's a > different story). > As I understand it, it gives you additional flexibility. You can have a single function that is linked to more than one widget. Widget name is available so function can behave differently. Currently I have e.g. function ((${+NUMERIC})) || zle .set-local-history if [[ $WIDGET == .* ]] then zle $WIDGET else zle .$WIDGET fi ((${+NUMERIC})) || zle .set-local-history and redefine all *history* widgets to use this function. Implementing the same directly as function would depend on FUNCTIONARGZERO setting. /andrej