Last active
August 29, 2015 13:57
-
-
Save bhyde/9515331 to your computer and use it in GitHub Desktop.
cl-launch doesn't read it's init file until you beg?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bash-3.2$ cl-launch --version | |
cl-launch 3.22.1 | |
Supported implementations: | |
sbcl, cmucl (lisp), clisp, ecl, ccl (openmcl), abcl, | |
xcl, gcl (gclcvs), allegro (alisp), lispworks, scl | |
Local defaults for generated scripts: | |
will search in this order these supported implementations: | |
sbcl clisp ccl ecl cmucl gclcvs lispworks allegro gcl abcl scl | |
will generate self-contained scripts using option --no-include by default | |
will not use /etc/cl-launchrc and ~/.cl-launchrc by default | |
will generate scripts that do not use clbuild by default | |
bash-3.2$ cat ~/.cl-launchrc | |
echo "Hi there." | |
LISPS=ccl | |
bash-3.2$ cl-launch -l ccl -ip '(lisp-implementation-type)' | |
Clozure Common Lisp | |
bash-3.2$ cl-launch -ip '(lisp-implementation-type)' | |
SBCL | |
bash-3.2$ cl-launch --rc -ip '(lisp-implementation-type)' | |
Hi there. | |
Clozure Common Lisp | |
bash-3.2$ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment