From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-40459-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 16535 invoked by alias); 29 Jan 2017 18:38:22 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 40459
Received: (qmail 14469 invoked from network); 29 Jan 2017 18:38:22 -0000
X-Qmail-Scanner-Diagnostics: from mercury.zanshin.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, 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.334164 secs); 29 Jan 2017 18:38:22 -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: Sun, 29 Jan 2017 10:37:41 -0800 (PST)
From: Bart Schaefer <schaefer@brasslantern.com>
Reply-To: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATH: autoload with explicit path
In-Reply-To: <1485711154.2495187.863317032.1E2B1AE2@webmail.messagingengine.com>
Message-ID: <alpine.LRH.2.00.1701291026360.4560@toltec.zanshin.com>
References: <CGME20170127151334epcas2p4c32b57f69fcae22b40b309793eb8ceb6@epcas2p4.samsung.com> <1485529979.987251.861563792.06CCDCAC@webmail.messagingengine.com> <20170127162440.10a5c85b@pwslap01u.europe.root.pri> <1485542415.1037033.861766968.196E6FB9@webmail.messagingengine.com>
 <20170127184448.5591e976@pwslap01u.europe.root.pri> <alpine.LRH.2.00.1701280959450.4560@toltec.zanshin.com> <20170128191248.4718b24c@ntlworld.com> <1485692865.2441595.863153472.2F8272F0@webmail.messagingengine.com> <alpine.LRH.2.00.1701290758180.4560@toltec.zanshin.com>
 <1485711154.2495187.863317032.1E2B1AE2@webmail.messagingengine.com>
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: TEXT/PLAIN; charset=US-ASCII

On Sun, 29 Jan 2017, Sebastian Gniazdowski wrote:

> I wrote earlier that -P (let's use your proposed option name) should
> prepend dirchache path to FPATH. In other words, -P causes any descent
> autoload to try dircache part first, then follow to process fpath.

That's still not sufficient for the general case, I think.  What happens
if two function suites have an autoload-dependency on one another, and
neither is in the default $fpath?