From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8780 invoked by alias); 9 Nov 2013 02:12:01 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 18128 Received: (qmail 2809 invoked from network); 9 Nov 2013 02:11:55 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <131108181143.ZM26121@torch.brasslantern.com> Date: Fri, 08 Nov 2013 18:11:43 -0800 In-reply-to: <20131108161109.6e373049@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: zsh 5.0.2-test-1 is available" (Nov 8, 4:11pm) References: <20131106202321.4a48c77b@pws-pc.ntlworld.com> <20131107153315.GW3544@sym.noone.org> <20131107160551.7aa195dc@pwslap01u.europe.root.pri> <20131107191806.GA85153@redoubt.spodhuis.org> <131107173627.ZM24325@torch.brasslantern.com> <20131108071627.GA6216@redoubt.spodhuis.org> <20131108093822.1534aa88@pwslap01u.europe.root.pri> <131108063903.ZM25660@torch.brasslantern.com> <20131108161109.6e373049@pwslap01u.europe.root.pri> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Peter Stephenson , zsh-users@zsh.org Subject: Re: zsh 5.0.2-test-1 is available MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Nov 8, 4:11pm, Peter Stephenson wrote: } } It seems to me it's equally not an error to mark zstat as a builtin from } zsh/stat if it's already loaded as a builtin from zsh/stat. It would } only be an error if there's a conflict. } } That's how "autoload" works, after all: it can't check for a conflict } (without major faff) but it does check if a function's already loaded. I'm confused; these statements seem contradictory, so I must be missing something. If we can't check for a conflict, how can we suppress the error message? I.e., how do we know that zstat is already loaded as a builtin from the same module we're now loading?