> Much less was I trying to criticize you,
Oh I didn't think you were :-)
> Just trying to raise awareness about (the few) shell variation idiosyncracies
> I know about, to help making people's lives easier.
Sounds good to me.
--
Cheers,
Clive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Aug 16, 2017 at 02:56:01PM +0100, Clive Standbridge wrote:
>
> > The "declare", OTOH, is pretty Bashist. But it can be replaced by
> > a simple "echo":
>
> True. It was just a convenient way of showing that the variable hadn't
> absorbed any
> The "declare", OTOH, is pretty Bashist. But it can be replaced by
> a simple "echo":
True. It was just a convenient way of showing that the variable hadn't
absorbed any white space.
Besides, I was just picking up the "Bash can't do it" gauntlet. I'd
often prefer awk in such a situation (like
> wooledg:~$ ip -o link | awk -F": " '{print $2}'
> lo
> eth0
>
> The only other scripting language I know that can do splitting with
> multi-character separators is perl.
>
> wooledg:~$ ip -o link | perl -ne '@x=split(/: /); print $x[1], "\n"'
> lo
> eth0
>
> Bash and Tcl can't do it, at
4 matches
Mail list logo
