From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8645 invoked from network); 7 Jun 1999 11:44:48 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 7 Jun 1999 11:44:48 -0000 Received: (qmail 19801 invoked by alias); 7 Jun 1999 11:44:32 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6497 Received: (qmail 19794 invoked from network); 7 Jun 1999 11:44:32 -0000 Date: Mon, 7 Jun 1999 13:44:28 +0200 (MET DST) Message-Id: <199906071144.NAA07107@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Andrej Borsenkow"'s message of Mon, 7 Jun 1999 15:15:36 +0400 Subject: Re: ** matching? Andrej Borsenkow wrote: > I understand, that it may be near to impossible to implement, but ... > > bor@itsrm2:/tools/src/zsh-3.1.5-pws-20%> view **/_brace_ > Beep > > bor@itsrm2:/tools/src/zsh-3.1.5-pws-20%> view */*/_brace_ > bor@itsrm2:/tools/src/zsh-3.1.5-pws-20%> view > Completion/Base/_brace_parameter > > I'm quite used to using ** ... so, any chance to use it in completion as > well? Well, first: you can always use expansion for things like this. Then: The problem is that we would suddenly have to deal with paths with different numbers of components. The easiest way to implement something like this which I can currently see is to have _path_files try */, then */*/, and so on, up to a configuarable maximum number of components. But if you have a/foo and a/b/foo, this would only complete the first one. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de