From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28173 invoked from network); 3 Nov 1998 15:15:41 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 3 Nov 1998 15:15:41 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id KAA18907; Tue, 3 Nov 1998 10:02:43 -0500 (EST) Resent-Date: Tue, 3 Nov 1998 10:02:43 -0500 (EST) Message-Id: <199811031501.PAA31047@diamond.tao.co.uk> Subject: Re: PATCH: 3.1.5 - (Sven) Case-insensitive globbing To: zsh-workers@math.gatech.edu Date: Tue, 3 Nov 1998 15:01:12 +0000 (GMT) From: "Zefram" In-Reply-To: from "Bruce Stephens" at Nov 3, 98 12:47:14 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"FnE8U.0.Jd4.IinFs"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4514 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >Approximate matching could either use the auto-correct code, or could >use something like whatever agrep uses. In the latter case, it would >have an optional integer parameter too, so "(#a1)readme" would match >"Readme" and "read.me", but to match "read", you'd need "(#a2)readme". Great idea. If this can be implemented cleanly, it's in. Let's be the first shell with approximate pattern matching (and approximate globbing) as a standard feature. >Hmm, maybe this could provide a way to configure the autocorrection >feature too? Maybe. The autocorrection could be implemented as a shell function, which by default uses fuzzy globbing to generate corrections. Is this what you have in mind? -zefram