On Fri, May 3, 2024 at 21:43 David Christensen <dpchr...@holgerdanske.com> wrote: ...
> My practice is to start with '#!/bin/sh' and migrate to '#!/usr/bin/env > perl' as complexity increases. I agree with David's direction, but ending with Raku instead of Perl. I don't think golfing is the way to illustrate a practical solution, so I show a short Raku script: $ cat read.raku #!/usr/bin/env raku my $a = "name with spaces"; my $b = "name\nwith newline"; say "file 1: |$a|"; say "file 2: |$b|"; And executing it: $ ./read.raku file 1: |name with spaces| file 2: |name with newlines| With Raku, it's easy to search the directory for the weird file names, open them, and use their contents. Raku also has many built-in quoting constructs to suit any situation. I'll be happy to demo any of that here. Best regards, -Tom
