From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13618 invoked from network); 12 Jul 2001 07:20:44 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 12 Jul 2001 07:20:44 -0000 Received: (qmail 11591 invoked by alias); 12 Jul 2001 07:20:37 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15379 Received: (qmail 11530 invoked from network); 12 Jul 2001 07:20:37 -0000 From: Sven Wischnowsky Date: Thu, 12 Jul 2001 09:18:11 +0200 (MET DST) Message-Id: <200107120718.JAA17621@beta.informatik.hu-berlin.de> To: zsh-workers@sunsite.dk Subject: Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n In-Reply-To: Peter Stephenson wrote: > "Bart Schaefer" wrote: > > On Jul 11, 1:30pm, Andrew Markebo wrote: > > } aes@NOCTURN:Jul04<130> cvs --help-options > > } zsh: correct 'cvs' to '_cvs' [nyae]? n > > > > Aside to zsh-workers: Regardless of the above, this really shouldn't > > happen. I'd hate to suggest special-casing a leading underscore in the > > correction code. Other possibilities? > > Well, the *real* fix is to make the correction code use the completion > system to generate corrections and do it with shell functions. But I > suspect that's a huge amount of work, since the completion system is > heavily tied into zle. I've been thinking about this ever since we added correction to the completion system... There's another problem, namely: where to make it try correction. After each word, but what exactly is a word here. And what about things like `../$foo/bar' -- it might be that it's the `$foo' that really should be `Foo' or whatever. Very complicated that. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de