Not a bug.
On Tue, Mar 31, 2015 at 06:04:53PM +0300, Filimonov Vadim wrote: [..] > filimonov@filimonov:~/bashbug/bash-4.3$ read -u63 LINE <(echo "*");echo $LINE > bash: read: `/dev/fd/63': not a valid identifier > ABOUT-NLS aclocal.m4 alias.c alias.h alias.o array.c arrayfunc.c arrayfunc.h > arrayfunc.o array.h array.o assoc.c assoc.h assoc.o AUTHORS bash bashansi.h > bashbug bashhist.c bashhist.h bashhist.o bashintl.h bashjmp You are storing a literal asterisk in the LINE variable, and then, you're expanding it without double quotes. One of the known side-effects of expanding a parameter without guarding it with double quotes is that pathname expansion occurs. Please, double quote "$LINE". Example: dualbus@yaqui:/$ v='*'; echo quoted: "$v"; echo unquoted: $v quoted: * unquoted: bin boot dev etc home initrd.img lib lib64 media mnt opt proc root run sbin srv sys tmp usr var vmlinuz -- Eduardo Bustamante | https://dualbus.me/
