Strange subrequest dir_config issue

2002-05-21 Thread Matt Sergeant
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is just a heads up on something I've not seen documented in either the Eagle book or in the Cookbook (at least not that I can find). If you create a subrequest via $r->lookup_file(), the per_dir_config entry doesn't seem to be created. If you

Re: Strange subrequest dir_config issue

2002-05-23 Thread Geoffrey Young
Matt Sergeant wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > This is just a heads up on something I've not seen documented in either the > Eagle book or in the Cookbook (at least not that I can find). > > If you create a subrequest via $r->lookup_file(), the per_dir_config entr

Re: Strange subrequest dir_config issue

2002-05-24 Thread Matt Sergeant
On Thu, 23 May 2002, Geoffrey Young wrote: > Matt Sergeant wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > This is just a heads up on something I've not seen documented in either the > > Eagle book or in the Cookbook (at least not that I can find). > > > > If you create a s

Re: Strange subrequest dir_config issue

2002-05-24 Thread Per Einar Ellefsen
At 12:38 24.05.2002, Matt Sergeant wrote: >Well it all made sense to me anyway - I just thought it should be >documented ;-) Thanks a lot Matt and Geoffrey, I have added this to the documentation (waiting for Stas to commit it). It seems to me that it's a more general problem with assuming too