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

[Peter Cordes]

BTW, upstream already had the no-results no-errors behaviour, so my
patch didn't actually change anything behaviour-wise in upstream, just
in trusty.

same change in  _quote_readline_by_ref():
-    [[ ${!2} == \$* ]] && eval $2=${!2}
+    [[ ${!2} == \$\'* ]] && eval $2=${!2}

I'd suggest going with upstream, not my patch, since I don't really
understand what's going on in that code >.<


** Summary changed:

- Bash completion within $( fails in Trusty
+ error messages completing args inside $()

-- 
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