On 29/08/06, Luca Capello <[EMAIL PROTECTED]> wrote:
check_lisp_variable () { test -r /etc/cl-launchrc && . /etc/cl-launchrc test -r "$HOME/.cl-launchrc" && . "$HOME/.cl-launchrc" test -n ${SOFTWARE_SYSTEM} && LISP=${SOFTWARE_SYSTEM} }
I have several issues with such a patch:
(1) I took enough pain to get cl-launch running on a wide variety of shells (bash, zsh, posh, dash...) and I won't accept any bash-ism. Eval is OK. (2) since we're using eval I'd rather the variable be named LISP_stumpwm or something like that. (3) this patch just won't work when we're in --dump mode, since it very wrongly overrides the $LISP from the dumped image. A script generated with --dump should NOT read any kind of cl-launchrc. (4) If you hack cl-launch, you might want to run cl-launch -l "clisp sbcl cmucl gcl" -B tests from a temporary directory (complete with all installed and supported implementations). This will run the self-test. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Amateurs talk strategy. Professionals talk logistics. - old military saying
