Many CL's offer a way to retrieve the Lisp script name, but CLISP appears to silently drop this information. I've managed a hack around this, but not without caveats.

A shebang line forces the script name onto the shell arguments twice, forcing it into ext:*args*. However, this method only works when the Lisp script is run with Unix ./ notation (chmod a+x && ./scriptname.lisp), and the script must be run with CLISP; Thus the script immediately loses portability to other CL's which require their own shebangs.

Could CLISP please provide an accessor similar to ext:*args* that exposes argv[0], as a C program would see it? Thank you.


Andrew Pennebaker