CLISP - an ANSI Common Lisp / Bugs / #716 CLISP not deleting the non-existent wildcard arguments

#716 CLISP not deleting the non-existent wildcard arguments

Milestone: lisp error

Status: closed-invalid

Owner: Sam Steingold

Labels: None

Priority: 5

Updated: 2017-11-20

Created: 2017-11-20

Creator: Jean Louis

Private: No

admin-> ls 
1536  320  400  640  800  PC090018.JPG
[~/public_html/images/2010/2010-12-09]
admin-> clisp ~/bin/rcd/prepare-images.lisp *.JPG *.jpg *
(PC090018.JPG *.jpg 1536 320 400 640 800 PC090018.JPG)
[~/public_html/images/2010/2010-12-09

Above is the result of the clisp on command line. I am using development version, latest.

The script is just showing the arguments.

If there is no file with lowercased *.jpg this argument is then not deleted from the argument list. I general the arguments shall be expaned, and if wildcard argument does not expand to any files, then it should not be in the argument list as "*.jpg"

Jean

Discussion

Jean Louis - 2017-11-20

... as "*.jpg"

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Sam Steingold - 2017-11-20

status: open --> closed-invalid

assigned_to: Sam Steingold

Group: ANSI compliance issue --> lisp error
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Jean Louis - 2017-11-21
  
  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
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Sam Steingold - 2017-11-20

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.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -11,7 +11,7 @@

 The script is just showing the arguments.

-If there is no file with lowercased *.jpg this argument is then not deleted from the argument list. I general the arguments shall be expaned, and if wildcard argument does not expand to any files, then it should not be in the argument list as "*.jpg"
+If there is no file with lowercased `*.jpg` this argument is then not deleted from the argument list. I general the arguments shall be expaned, and if wildcard argument does not expand to any files, then it should not be in the argument list as `"*.jpg"`

 Jean

CLISP not deleting the non-existent wildcard arguments

Group

Searches

Help

#716 CLISP not deleting the non-existent wildcard arguments

Discussion