From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-23744-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 4243 invoked from network); 6 Aug 2007 02:36:52 -0000
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.1
Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88)
  by ns1.primenet.com.au with SMTP; 6 Aug 2007 02:36:52 -0000
Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts)
Received: (qmail 39484 invoked from network); 6 Aug 2007 02:36:46 -0000
Received: from sunsite.dk (130.225.247.90)
  by a.mx.sunsite.dk with SMTP; 6 Aug 2007 02:36:46 -0000
Received: (qmail 1136 invoked by alias); 6 Aug 2007 02:36:44 -0000
Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 23744
Received: (qmail 1126 invoked from network); 6 Aug 2007 02:36:44 -0000
Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88)
  by sunsite.dk with SMTP; 6 Aug 2007 02:36:44 -0000
Received: (qmail 39217 invoked from network); 6 Aug 2007 02:36:44 -0000
Received: from rv-out-0910.google.com (209.85.198.185)
  by a.mx.sunsite.dk with SMTP; 6 Aug 2007 02:36:40 -0000
Received: by rv-out-0910.google.com with SMTP id g11so898899rvb
        for <zsh-workers@sunsite.dk>; Sun, 05 Aug 2007 19:36:38 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=awhcZrM38F/LUGQBpv9JI2csrnhnkl9kJpbe9U0CQISW16DQ6FcUGokDMmjEDlxCB1hyR3EGnkQBS5UYo2qhjWH2rto8C6LeKua9Lcy35ZhCY2KQp+7xsE56mL+y9il8yf50YCO2TdbHNyyLLpb/LnZ74npLCviZdXgByW12N08=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=PWYC0UAI/VlDjng4pvCM5r/F22gIN8EiHGFMu/r9x5Og8TnBfyaLj92kFtejEmp5Aqwho/AYKlhRQUSx+sVrFxmxyASV3T6OCavbZYJR2Z3Z/LEU8r9EJ9hKpV2/SlCK2lOHZX+nQ2bIOz7AJ0/W0WgQ3jOQGmZUtR6zU/GAWOw=
Received: by 10.142.185.13 with SMTP id i13mr228477wff.1186367798315;
        Sun, 05 Aug 2007 19:36:38 -0700 (PDT)
Received: by 10.143.43.10 with HTTP; Sun, 5 Aug 2007 19:36:38 -0700 (PDT)
Message-ID: <17393e3e0708051936m388bf6e4pdca167f03b8dcd5c@mail.gmail.com>
Date: Sun, 5 Aug 2007 22:36:38 -0400
From: "Matt Wozniski" <godlygeek@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Unexpected side effect of 'setopt correct'
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I just noticed this effect of 'setopt correct'.. Is this intentional behavior?

~> zsh -f
mastermind% setopt correct
mastermind% pid() {
zsh: correct 'pid' to 'pic' [nyae]? %


mastermind% function pid() {
function>
mastermind%

Is it intentional that it attempts to correct on a function
definition?  Is it intentional that it only attempts to correct one of
the two types of function definition?  Something about this behavior
caught me off guard.  :)

~Matt