Juho Snellman <jsnell@...> writes:
> "Tobias C. Rittweiler" <tcr@...> writes:
> > Hi,
> > (open "/tmp/foo*.lisp") where the file `foo*.lisp' does in fact exist in
> > /tmp/ signals an error about "bad place for a wild pathname."
> > Next to knowing nothing about CL's pathname machinery, is this behaviour
> > sensible? If yes, what can I do about it?
> It's at least justifiable. The alternative would be for (directory
> "/tmp/foo*.lisp") to not do what people expect. You can write
> "/tmp/foo\\*.lisp" instead, or have a look at sb-ext:parse-native-namestring.
Thanks for the prompt answer. I encountered this error by trying to C-c
C-k a file named `let*.lisp'.
Is calling SB-EXT:PARSE-NATIVE-NAMESTRING without any further arguments
sensible in the relevant bits of SBCL's SWANK backend? (It seems to DTRT
for the example under discussion, but I'd like to double-check because I
can't say that I comphrehend what its docstring wants to tell me.)