From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20650 invoked from network); 14 Dec 1999 09:26:37 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Dec 1999 09:26:37 -0000 Received: (qmail 13892 invoked by alias); 14 Dec 1999 09:26:32 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9032 Received: (qmail 13879 invoked from network); 14 Dec 1999 09:26:32 -0000 Date: Tue, 14 Dec 1999 10:26:30 +0100 (MET) Message-Id: <199912140926.KAA29080@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Peter Stephenson's message of Mon, 13 Dec 1999 21:31:10 +0000 Subject: Re: PATCH: Add jobdirs association to parameter module Peter Stephenson wrote: > ... > > It's a shame we didn't have more specific names for parameters, since the > parameter module is quiet heavily used in completion, so there is quite a > lot of name space pollution. They stop being special if made local, but > it's still a problem. The ksh mechanism ${.param.jobdirs} would be > excellent for this. When I last added parameters to it, I asked if I should rename them to `z...' -- we decided against that. I agree that it would be nice to have this cleaner so I just tried to allow dots in parameter names by simply adding `typtab['.'] |= IIDENT;' to inittyptab(). It /seems/ to work, only `$.a.b' doesn't (but `${.a.b}' does), haven't found the place where it fails yet -- mainly because I haven't really searched for it. So, can anyone think of a good reason why we shouldn't do that? Like Peter (at least I think Peter meant that) I prefer the solution with the dots over the solution with just prepending a `z' before every parameter name. It's clean, it's extensible... Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de