From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4333 invoked by alias); 18 Jan 2017 00:07:02 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 40377 Received: (qmail 22429 invoked from network); 18 Jan 2017 00:07:02 -0000 X-Qmail-Scanner-Diagnostics: from mercury.zanshin.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(64.84.47.142):SA:0(-0.0/5.0):. Processed in 1.417211 secs); 18 Jan 2017 00:07:02 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at ipost.com designates 64.84.47.142 as permitted sender) Date: Tue, 17 Jan 2017 16:06:22 -0800 (PST) From: Bart Schaefer Reply-To: Bart Schaefer To: zsh-workers@zsh.org Subject: Re: PATCH: autoload with explicit path In-Reply-To: <20170117221754.GA14818@fujitsu.shahaf.local2> Message-ID: References: <20161211221844.5e51affe@ntlworld.com> <161212080550.ZM935@torch.brasslantern.com> <20161212163124.6654f077@pwslap01u.europe.root.pri> <20170110193102.7725620a@ntlworld.com> <20170117183606.5d1db3de@pwslap01u.europe.root.pri> <20170117221754.GA14818@fujitsu.shahaf.local2> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) X-Face: "f/X=UCVgd*^c>+x(gMq0at?e:woX+;'snkkRzc3SX<0AZ (/PS4.M2hzGS9X:Qj]at_H/%a9K}:-eS<"v_7vX84PG9Bf Zpb`wI!I4geY=or+nWq`3CX`oq&TJR;g^ps|7(MH?jh;bs %vHJfCh5>a*6Re5m|Bidja\\o]>n\A)ib1:yX*T`zR(*h~ %tOw<~!D9{e6h!8M2:d8G2@K>y^1I_Vdy\d\MYe]z7c MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1413522991-1513637508-1484697982=:4560" --1413522991-1513637508-1484697982=:4560 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT On Tue, 17 Jan 2017, Daniel Shahaf wrote: > Peter Stephenson wrote on Tue, Jan 17, 2017 at 18:36:06 +0000: > > I think this is the right way of doing it as the explicit > > path should continue to override the more vague autoload with no path > > indicated, and this is safer in case some code decides it needs a > > function and inadvertently resets the path the user carefully decided to > > give the function. > > Suppose $^fpath/foo/bar(N) has two matches, how do I explicitly autoload > the second one? I.e., how do I disambiguate «autoload foo/bar» (with no > leading slash) to load a particular copy of foo/bar? How does any of this interact with searching for functions inside files built with zcompile? (Does zcompile even support having a function name that contains a slash?) --1413522991-1513637508-1484697982=:4560--