[Bug 1312243] Re: Bash completion within $( fails in Trusty

[Marcelo do Pagode]

This bug, filed in 2011 and fixed in 2012 seems similar (same error message: missing closing matching delimiter):
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/772571

Since this bug has been fixed then, I hope it can at least shed some light on the current one.
PS: I'm using Trusty as well, having the same error when using $( in a bash for loop:
$for f in $(cat exam[TAB]bash: unexpected EOF while looking for matching `)'
bash: syntax error: unexpected end of file

Cheers!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash-completion in Ubuntu.
https://bugs.launchpad.net/bugs/1312243

Title:
  Bash completion within $( fails in Trusty

Status in “bash-completion” package in Ubuntu:
  Confirmed
Status in “bash-completion” package in Debian:
  New

Bug description:
  Hello. Please observe the following transcript (only [TAB] has been
  inserted to indicate the position where I hit TAB):

  In Trusty:

  $ cat <<EOF > foo
  > Test
  > EOF
  $ echo $(< foo)
  Test
  $ echo $(< fo[TAB]bash: unexpected EOF while looking for matching `)'
  bash: syntax error: unexpected end of file
  ^C
  $ echo $(cat fo[TAB]bash: unexpected EOF while looking for matching `)'
  bash: syntax error: unexpected end of file

  In Saucy:

  $ cat <<EOF > foo
  > Test
  > EOF
  $ echo $(< foo)
  Test
  $ echo $(< fo[TAB]o^C
  $ echo $(cat fo[TAB]o^C

  Simply put, once I start a command substitution with $( I am not able
  to use the [TAB] completion in Trusty any longer while this was
  working file in Saucy. I hope this can be fixed soon since it really
  hampers use of the command-line. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1312243/+subscriptions