From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18363 invoked from network); 21 Apr 2000 00:48:12 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 21 Apr 2000 00:48:12 -0000 Received: (qmail 17298 invoked by alias); 21 Apr 2000 00:48:01 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10886 Received: (qmail 17285 invoked from network); 21 Apr 2000 00:48:00 -0000 Message-ID: <20000421004758.23026.qmail@web1303.mail.yahoo.com> Date: Thu, 20 Apr 2000 17:47:58 -0700 (PDT) From: Felix Rosencrantz Subject: BUG: Matching cause character to be deleted. To: zsh-workers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Since, I offered to add the example to the documentation, I was starting to look at the suggested matching specification that Sven suggested for dealing with anchors between numbers and upper case letters, so f2 could match file2, and IR2 could match IndianRed2. I found this bug, which is pruned down. myprompt@ zsh -f host% mkdir j host% touch j/{BW,UWB,W} host% bindkey -e; autoload -U compinit; compinit -D host% zstyle ':completion:*:complete:*' matcher-list 'r:|[A-Z0-9]=*' host% ls j/W #Tab deletes the W, so the line looks like this: host% ls j/ Though, the matching specification suggested seems to comes pretty close to what I want, it still has some odd behaviors when handling filenames that contain upper case words, like ABCdef. Matching seems to match in the middle of words, which doesn't quite feel right. It would nice if it was possible to specify gaps between characters as anchors, even if it would make it more difficult to understand matching specifications. (Though, I'm challenged by just writing specifications, I'm not offering to modify the code. ) -FR __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.com