2019-09-25 15:33:24 -0500, Eric Blake:
[...]
> Bash scripts often begin with @code{#! /bin/bash} (assuming that
> Bash has been installed in @file{/bin}), since this ensures that
> Bash will be used to interpret the script, even if it is executed
> -under another shell.
> +under another shell.
Just because Linux does not split whitespace on #! lines does not mean
that all operating systems behave the same. Mention the recent
coreutils 8.30 'env -S' addition for working around interpreter
argument limitations, as well as the use of env to locate bash even
when it is not in /bin.
---
do
On 9/25/19 2:11 PM, Ole Tange wrote:
> I think you are right. The goal is to emulate 'ls'.
>
> As you can see from GNU Parallel's manual I would use printf instead:
>
> printf '%s\0' * | parallel -0 mv {} destdir
This is the best option, with the usual caveat about having to change the
patt
On Mon, Sep 23, 2019 at 3:53 PM Chet Ramey wrote:
>
> On 9/23/19 5:29 AM, Ilkka Virta wrote:
> > On 22.9. 21:15, Chet Ramey wrote:
> >> On 9/20/19 10:24 PM, hk wrote:
> >>
> >>> Description:
> >>> On the section 3.2.6(GNU Parallel, page 16 in the pdf) of Bash
> >>> Reference Manual. The m
