On 8/17/07, Jason Aiken <email@example.com> wrote:
> I use an init.acl file in the custom/init directory to run a source
> command for each ACL file in the custom/scripts directory.
Thanks for the thought, Jason.
That's way preferable to making changes in the install tree. In order to
further enhance the transparency of such a modification, I would follow the
strategy I use for all such code in either editinit or init. That is, create
an individual, eponymous acl file. This one would be:
I prefer the clutter of files but being able to see what's being set where.
(I don't go as far as including the set value, for example, it's
set_gentextwarnings.acl, not set_gentextwarnings_0.acl.
Really, I just wanted to use the word eponymous.
All that said, I still don't understand why having the file in scripts
doesn't capture the package/function call. I think it should. It's working