Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: 3.1.5 - (Sven) Case-insensitive globbing
- X-seq: zsh-workers 4512
- From: Bruce Stephens <b.stephens@xxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: PATCH: 3.1.5 - (Sven) Case-insensitive globbing
- Date: 03 Nov 1998 12:47:14 +0000
- In-reply-to: Bruce Stephens's message of "03 Nov 1998 12:22:47 +0000"
- References: <199811030812.JAA23176@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <vbn269dkyw.fsf@xxxxxxxxxxxxxxx>
- Sender: B.Stephens@xxxxxxxxx
Bruce Stephens <b.stephens@xxxxxxxxx> writes:
> Yes, maybe. I thought of another example: approximate matching.
>
> 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".
>
> Hmm, maybe this could provide a way to configure the autocorrection
> feature too?
This would provide useful implementation parts anyway---given some way
of specifying a function that could operate on a possibly miss-spelled
word, approximate globbing would provide a natural way of generating a
sensible alternative (or alternatives).
Messages sorted by:
Reverse Date,
Date,
Thread,
Author