From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22172 invoked by alias); 29 Jan 2017 16:11:44 -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: 40455 Received: (qmail 446 invoked from network); 29 Jan 2017 16:11:44 -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.55242 secs); 29 Jan 2017 16:11:44 -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 08:11:04 -0800 (PST) From: Bart Schaefer Reply-To: Bart Schaefer To: zsh-workers@zsh.org Subject: Re: PATH: autoload with explicit path In-Reply-To: <1485692865.2441595.863153472.2F8272F0@webmail.messagingengine.com> Message-ID: References: <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> <20170128191248.4718b24c@ntlworld.com> <1485692865.2441595.863153472.2F8272F0@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: > To make the new feature complete, absolute paths must descent to > autoloaded functions. Keeping the absolute path only to directly > autoloaded function is ersatz. It's a half-step. I autoload single > function, and then FPATH again takes control and does the "imagine the > layers" thing. This is a tragedy. Respectfully, Sebastian, I disagree. Consider for example that several of the autoloadable functions in the zsh distribution rely on "autoload colors". If autoload behaved the way you suggest, this would break, because the colors function would not be found at the absolute path from which the calling function was loaded -- unless the writer of the calling function has used "autoload -d", of course. But if we're now relying on the author to use the correct options for autoload, we're right back where we started -- might as well rely on the author to make his function suite "relocatable" by way of $function_source as well, and that is now possible. There's no magic solution that automatically covers all the variations without cooperation from both the writer and the installer of the suite.