From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6631 invoked by alias); 28 Jan 2017 19:46:11 -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: 40443 Received: (qmail 5636 invoked from network); 28 Jan 2017 19:46:11 -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.596989 secs); 28 Jan 2017 19:46:11 -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: Sat, 28 Jan 2017 11:45:36 -0800 (PST) From: Bart Schaefer Reply-To: Bart Schaefer To: zsh-workers@zsh.org Subject: Re: PATH: autoload with explicit path In-Reply-To: <20170128191248.4718b24c@ntlworld.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> 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 Sat, 28 Jan 2017, Peter Stephenson wrote: > On Sat, 28 Jan 2017 10:05:46 -0800 (PST) > Bart Schaefer wrote: > > If every autoload were relative to the absolute-path information of the > > calling function context, Sebastian's plan would work without needing > > to edit anything, provided that he autoloads the bootstrap function with > > an absolute path. > > I'm afraid this is just confusing matters. Sebastian was asking for a > new option. Well yes, the option would be on the autoload of the bootstrap function, i.e., autoload -P /some/hard/path/foo where "foo" in turn calls "autoload bar" would cause the autoload of bar to inherit /some/hard/path from foo. > There's no question of changing the default behaviour Indeed not. ("-P" chosen for example only and entirely without reference to whether it conflicts with some other use of -P in typeset/functions/etc.)