Opened 20 months ago

Last modified 20 months ago

#452 new defect

Pathname functions do the wrong thing when faced with actual filename with embedded asterisk

Reported by: mevenson Owned by:
Priority: major Milestone: 1.6.0
Component: java Version: 1.5.0-dev
Keywords: Cc:
Parent Tickets:


From <>

In a shell:

touch /tmp/*

(probe-file "/tmp/")
; Evaluation aborted on #<FILE-ERROR {7DF4B809}>.
CL-USER> (probe-file "/tmp/\")
; Evaluation aborted on #<FILE-ERROR {4D5E9779}>.
CL-USER> (probe-file "/tmp/%2A")
CL-USER> (probe-file "file:///tmp/%2A")
; Evaluation aborted on #<FILE-ERROR {7DF4B809}>.

The error is: Bad place for a wild pathname.

I had a quick look to see how this could be repaired, but wasn't sure what the right approach is. This stackoverflow answer suggests using "\" as a quote, which is probably the best solution, and would be compatible with what Clozure CL, SBCL and LispWorks? do. I also think the percent escaped character should be made to work.

The specific screw case I had was that there was an accidentally created file with a "*" in a directory that was being scanned for ASDF's system registry, which crapped out because the directory function returned the "*" pathname, and subsequently did a probe on the file.

Subtickets (add)

Change History (1)

comment:1 Changed 20 months ago by mevenson

  • Component changed from (A)MOP to java
  • Milestone set to 1.6.0
  • Version set to 1.5.0-dev
Note: See TracTickets for help on using tickets.