From: James Y K. <fo...@fu...> - 2010-10-13 12:40:21
|
On Oct 13, 2010, at 3:42 AM, Peter Keller wrote: > #! /usr/bin/sbcl --script --prepend-libraries-path ./stuff --fasl-dir ./fasls > (format t "HI~%") > > so I can run my script on machines that have SBCL, but might not have > my needed libraries, so I include them and a place to find/build them. It's not necessary for all that to be a command-line option: you should be able to set variables/call functions to effect that at the top of your script code. They just need to be well-documented. On Oct 13, 2010, at 4:22 AM, Didier Verna wrote: > [1] because executing a zsh script doesn't prevent zsh from reading > .zshenv, and here I rejoin Nikodemus on the interactive/non-interactive > distinction. Yeah, but that's a strange and unique zsh behavior. And it's definitely caused strange problems for me in the past (my fault, yes, but still). Neither traditional sh nor bash source *any* config files at all when running scripts. And I don't see why SBCL and ASDF really need to either, so long as it starts out life looking for libraries in $LISPPATH, /usr/somelocation, and ~/.somelocation. James |