It seems that $COMP_WORDBREAKS annoys users when filenames contain
one of its characters:
http://lists.gnu.org/archive/html/bug-bash/2005-07/msg00034.html
http://lists.gnu.org/archive/html/bug-bash/2006-09/msg00019.html
http://lists.gnu.org/archive/html/bug-bash/2011-02/msg00163.html
and my b
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
-
On Wednesday, May 23, 2012 09:47:33 PM gregrwm wrote:
> expansion anomaly with quoted and concatenated positional parameters
Also reproducible in 4.2.28(1)-release
This occurs when any expansion is adjacent to or contained within a word that
is adjacent to an expansion of the from "$@" or "${a[@]
Ugh, Sorry, I forgot to strip trailing whitespace. If that wasn't
comprehensible for anyone, the heredoc in the preceeding the testcase was:
args() { printf '<%s> ' "$@"; echo; }
args "${@}${1}"
args "${@}foo"
args ${@}${1}
args ${@}foo
IFS=
args ${@}${1}
args ${@}foo
EOF
--
Dan Douglas
