From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26721 invoked from network); 17 May 2000 04:12:37 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 17 May 2000 04:12:37 -0000 Received: (qmail 5443 invoked by alias); 17 May 2000 04:12:19 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11427 Received: (qmail 5436 invoked from network); 17 May 2000 04:12:19 -0000 Message-ID: <20000517041158.9274.qmail@web1303.mail.yahoo.com> Date: Tue, 16 May 2000 21:11:58 -0700 (PDT) From: Felix Rosencrantz Subject: Re: PATCH: Completion matching control test. (Try 2) To: zsh-workers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Bart Schaefer wrote: > This works for me: > > print -lr "COMPADD:{${match[6]//[$'\r\n']/}}" > > Normally $'...' isn't expanded inside double quotes, but because it's > inside an embedded ${...} expansion, the rules get bent. Great. Works for me, too. Will use that. I'll send a patch when the changes make it into the repository. I don't think there is a need for try 3. > I suspect the other failed tests are confusion over `*' vs. `**' in the > matcher patterns, but I'm not sure. For example, the test Drat, I don't have any tests that use the double star syntax... I used several recent versions of zsh to create the output for the tests, plus a little hand-editing. Sven's changes have fixed some problems, that I might have left in, because I'm unclear on what the proper result should be. Like the problem report from workers/11388. Hopefully the test will help. I think matching control is great. -FR. __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/