From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29526 invoked from network); 31 Aug 1999 16:25:10 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 31 Aug 1999 16:25:10 -0000 Received: (qmail 22482 invoked by alias); 31 Aug 1999 16:24:59 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7582 Received: (qmail 22475 invoked from network); 31 Aug 1999 16:24:58 -0000 To: zsh-workers@sunsite.auc.dk Subject: Re: 6-pws-2 References: <199908311238.OAA29874@beta.informatik.hu-berlin.de> MIME-Version: 1.0 (generated by AKEMI 1.13.2 - =?ISO-2022-JP?B?Ig==?= =?ISO-2022-JP?B?GyRCQTA0Y0s8GyhCIg==?=) Content-Type: text/plain; charset=US-ASCII From: Tanaka Akira Date: 01 Sep 1999 01:19:53 +0900 In-Reply-To: Sven Wischnowsky's message of "Tue, 31 Aug 1999 14:38:58 +0200 (MET DST)" Message-ID: User-Agent: Chao-gnus/6.12.5 AKEMI/1.13.2 (=?ISO-2022-JP?B?GyRCQTAbKEI=?= =?ISO-2022-JP?B?GyRCNGNLPBsoQg==?=) FLAM-DOODLE/1.12.6 (=?ISO-2022-JP?B?GyRCM3cbKEI=?= 10R4.0/5.0) Emacs/20.4 (sparc-sun-solaris2.6) MULE/4.0 (HANANOEN) In article <199908311238.OAA29874@beta.informatik.hu-berlin.de>, Sven Wischnowsky writes: > > In article <9908301600.AA12634@ibmth.df.unipi.it>, > > Peter Stephenson writes: > > > - Personally, I prefer one single completion function for a suite of > > > related commands like cvs or pbm, since the accumulated clutter (and > > > added time to process completion files the first time) is large. If it > > > stays the way it is I will change the default for function installation > > > to keep the subdirectories. I think making cache file for each directory in fpath reduce start time. Because the directory that contains many files --- /usr/local/share/zsh/functions --- is stable in many case (except for some zsh developpers). > > > > The separation is sometimes useful for custumizations because we can > > override each function individually. These functions behaves like `hook'. > > I think it is useful that making hooks more easily without adding new files. > > Hm. How about making it a bit like a state machine: I feel that a state machine is the good abstraction for command line parsing. # I suspect that most command line structures can be represented by # regex. > Would that be acceptable to everyone? Can anyone think of ways to help > users write such state-machine functions? Hm. I think it is reasonable to implement a state as a function. A state transition can be represented as return from the function with next state. -- Tanaka Akira