I'm currently using the Cygwin package of clisp 2.33.1, and
I think command line arguments are processed somewhat differently
that what is advertised in the man (or with --help). My problem
is with -i and the 'terminal' lisp-file argument.
When I use only the terminal lisp-file argument, everything
works as expected : the first line (#!/.../clisp) is not
interpreted as lisp code, my RC file is not loaded, command-
line arguments situated after the lisp-file name are available
in ext:*args* and when the file is loaded, clisp terminates.
Example: 'clisp toto.lisp 1 2 3'
But as soon as I try using a -i initfile option in my command
line, it does not work anymore as above :
- the #! line in the lisp-file causes a read error,
- my RC file is loaded prior to everything else, even the initfile,
- no command-line arguments are available (ext:*args* is NIL),
- worse, trailing command-line arguments are interpreted as
lisp files to be loaded
- and finally, clisp enters a REPL.
Example: 'clisp -i initfile.lisp toto.lisp 1 2 3'
There is no indication of incompatibility between -i options
and the terminal lisp-file argument in the man, so I am a bit
surprised. I also have a clisp distribution on Debian GNU/Linux
but I have not tried the same experiment yet.
Is it a bug? Is it an 'undocumented feature'? Is there some
I'd like to have answers to those questions but I want to
thank all contributors to the clisp projet for their great