From: Nikodemus S. <nik...@ra...> - 2008-10-07 14:31:07
|
On Tue, Oct 7, 2008 at 4:54 PM, Zach Beane <xa...@xa...> wrote: > Same as with shell scripting; that is, there's nothing standard, and > if a script wants to add extra configuration, it does it by sourcing > some other file, or just including the configuration directly in the > script. The interactive user startup files are not sourced by default. I think Perl might be a better comparison here, though -- shell scripting is not know for the massive amounts of libraries used... Loading nothing has the benefit that everything is explicit, and it should be clear why a library is not found if it not found -- but it seems moderately painful for using non-standard libraries that you have not manually symlinked to ~/.sbcl/systems/. One possibility would be to skip initfiles, but add .asdfrc which would be loaded along with ASDF when the script for (require :asdf). Cheers, -- Nikodemus |