I understand the argument that strengthening our own CLI and shell-script practice to guard against spaces in filenames is both learned and good defense, as in, "don't go into battle without some armor protection." I do that when I'm really worried, and if you want to see how big shell scripts can get dealing with this, just look at the lengths to which many GNU scripts go to work safely in the jungle of filesystems and user preferences.
What I've found though, unless I'm actually using those greatly fortified GNU scripts and tools, is that sometimes ordinary pipelines on the CLI can get tripped up by spaces. So my approach has been to disarm the shooter, take the gun way, i.e., remove the space and replace it with a hyphen. I apologize, my beloved Racket, I don't mean to suggest in any way that you are a shooter, you most certainly are not, you are most benevolent, even as you are powerful. I'm only talking about the space. -- 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.
