-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/9/14, 9:14 AM, Eric Blake wrote:
> No, with bash 3.2, you are tripping up on a parser bug. Bash 3.2
> incorrectly handled double quotes inside unquoted parameter
> expansion.
This is mostly true, but it has nothing to do with the parser. This was
a change to how word expansion behaved, nothing more.
- --
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
iEYEARECAAYFAlSHCuIACgkQu1hp8GTqdKtjCgCbBF3Zf4K4x5Zm0JONdTTudsKh
NYwAn0xubauigzmr23pn7dQYnZ3ckp+D
=iPhY
-----END PGP SIGNATURE-----
