Re: Global variable modification by nameref chain

On 6/14/16 12:16 PM, Dan Douglas wrote: > On Sun, Jun 12, 2016 at 8:33 PM, Chet Ramey wrote: >> 3. Honor the assignment and delete the nameref variable, creating a new >>one, like bash-4.3: >> >> $ ../bash-4.3-patched/bash ./x1 >> declare -n a="b" >> declare -n b="a[1]" >> declare -a a='([1]="

Re: Multi-line, double quoted string triggers history expansion on subsequent single-quoted commands it gets piped to

On 6/14/16 8:52 AM, Néstor Tejero wrote: > When printing a multi-line string and piping to another command that uses > single-quotes, Bash tries to perform history expansion: > > echo "9 >> 10 >> 9 >> 11" | awk '!seen[$0]++' > bash: !seen[$0]++': event not found History expansion is explicitly l