[Bug 1312243] Re: error messages completing args inside $()

[Malte Skoruppa]

Looking at the aforementioned patch, it appears that it was made by Juan
Ciarlante to fix this bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739835

However, it also introduced the bug described in the current bug report.

Using the unpatched, upstream version of bash-completion, I still cannot
reproduce the #739835 Debian bug in Ubuntu 14.04. Maybe Juan's patch is
not necessary any longer?


** Bug watch added: Debian Bug tracker #739835
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739835

-- 
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:
  error messages completing args inside $()

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