On Sat, May 6, 2017 at 4:25 PM, Chet Ramey wrote:
[...]
> Thanks for the report. This will get fixed.
I'm not sure if this one is related to the above, or a different bug.
But I'm leaving it here anyways in case it helps:
(gdb) r -c 'read -n 128 < foo'
Starting program: /bash/bash -c 'read -n
On 5/5/17 1:45 AM, Eduardo Bustamante wrote:
> dualbus@debian:~/bash-fuzzing/read$ cat -A 6b
> M-^_0^A\$
> ^N
>
> dualbus@debian:~/bash-fuzzing/read$ od -c 6b
> 000 237 0 001 \ \n 016
> 006
>
> (gdb) file ~/src/gnu/bash/bash
> Reading symbols from ~/src/gnu/bash/bash...done.
> (gdb)
On 5/4/17 5:00 PM, Ángel wrote:
> No. IMHO the fix would be to expand ~ at assignment time, even when
> quoted, ie. PATH='~/bin' would be equivalent to PATH=~/bin
No. The semantics of expansion in quoted strings are well defined.
Performing tilde expansion on a quoted string in an assignment stat
On 5/3/17 6:40 PM, Nikolay Aleksandrovich Pavlov (ZyX) wrote:
> Bash Version: 4.3
> Patch Level: 48
> Release Status: release
>
> Description:
> If $PATH in bash contains ~ (e.g. `PATH='~/bin'`) it is incorrectly
> treated
> as if $HOME is present.
Yes. This is one of the oldest fe
