Jean Louis

On Mon, Nov 20, 2017 at 01:50:42PM -0000, Sam Steingold wrote: status: open --> closed-invalid assigned_to: Sam Steingold Group: ANSI compliance issue --> lisp error Comment: This is not a bug in CLISP, but rather the normal well-documented unix shell behavior. Try echo *.JPG *.jpg to see whih arguments the shell passes to CLISP. I was testing with perl, and it was removing those arguments. Alright, now I just need to remove them myself. Thanks for letting me know. Jean

On Mon, Nov 20, 2017 at 03:29:28PM -0000, Sam Steingold wrote: Bruno, I think I have a completely backwards compatible solution: the only people who would ever need it are those whose script names contain spaces. Those people will need to add -q to the shebang line in their scripts and call their scripts from the command line with clisp -q "my script with spaces.lisp" instead of clisp "my script with spaces.lisp". In fact, NO action is needed at ALL: -q is ignored (because it is the default) in scripts....

... as "*.jpg"

CLISP not deleting the non-existent wildcard arguments

On Sun, Nov 19, 2017 at 08:18:16PM -0000, Sam Steingold wrote: please use proper markup and the "eye" button in the upper right corner for preview. That I do not know what you mean. I am just using reply by email. the current clisp (hg tip) installs clisp! for scripting. if you do not see it, please debug why. I totally found it, it was my mistake not to see new executable file and symlink it (stow it). Jean

On Sun, Nov 19, 2017 at 06:06:15PM -0000, Sam Steingold wrote: you forgot to do make install Of course I did that. My clisp is installed as symlink under /usr/bin/clisp that points to /package/prog/clisp/bin/clisp and as such it does not work with the solution of !/usr/bin/clisp! and that solution seem not reasonable to me. -- Jean Louis

On Sun, Nov 19, 2017 at 05:21:20PM -0000, Sam Steingold wrote: replace the 1st line in your script with ``` !/usr/bin/clisp! -q -norc ``` my file is named locLink $ locLink bash: /home/data1/protected/bin/locLink: /usr/bin/clisp!: bad interpreter: No such file or directory Jean

As I am now using new version of CLISP with the spaces being handled, now I have problems in runing the script that begins with: !/usr/bin/clisp -q -norc (print "Hello") (exit) GNU CLISP: invalid argument: '-q -norc' GNU CLISP: use '-h' for help It works from a command line. It does not work any more from a script. Jean