(system* "/usr/local/bin/wget" "http://google.com"; "-O /tmp/fooflaksdjdghk")
The process wants "-O" here to be an argument by itself.
Okay, it's transforming -O into -o. Let's try the long form:
That happened because `wget` thought that you were still in the server authority host part of the URL, which in alphabetic case-insensitive, and it's normalizing the case. :)
Yep, that works. Okay, now let's try it with an actual filename,
Yes, that's a good way to do it. Or one argument for "-O" and another for the filename.
/tmp/Sara's birthday, 9/12/01-18/181: No such file or directory
The "/" in the filename is a separate problem, which actually has nothing to do with shell special character command line escaping/quoting. If you're on a Unix derivative OS, it normally expects "/" to be a directory separator in a file pathname (although maybe your OS does something different), so it thinks you're talking about a file under the "181" directory, which doesn't exist. So this error is due to something that is happening within or under the `wget` process (which is very much a Unix tool), either in its own code, in filesystem routines it uses, or in the OS services it's calling. Probably you don't want to put "/" in filenames, because, even if your current OS supports it, most filesystems and cloud storage interfaces will not.
-- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
