Debian Bug report logs - #272660
bash: completion of env vars broken (leading slash is added)

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Andreas Leitner <nozone@sbox.tugraz.at>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: bash: completion of env vars broken (leading slash is added)

Date: Tue, 21 Sep 2004 12:16:49 +0200

Package: bash
Version: 3.0-6
Severity: normal
Tags: sid

Since I upgraded from bash version 2.05a.0(1) the tab-completion for environment variables seems to be broken. When I for example enter "cd $HOM" and then hit TAB, it gets completed to "cd \$HOME" instead of "cd $HOME" which the older version of bash completed to.

many thanks in advance,
Andreas

-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux graz 2.6.7 #1 Mon Jun 28 22:34:29 CEST 2004 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages bash depends on:
ii  base-files                  3.0.2        Debian base system miscellaneous f
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libncurses5                 5.4-3        Shared libraries for terminal hand
ii  passwd                      1:4.0.3-17   Change and administer password and

-- no debconf information

Message #10 received at 272660@bugs.debian.org (full text, mbox, reply):

From: Andreas Leitner <nozone@sbox.tugraz.at>

To: 272660@bugs.debian.org

Subject: debugging

Date: Mon, 04 Oct 2004 01:37:35 +0200

I did some debugging and have now a vague idea of what goes wrong.
The problem only happens once /etc/bash_completion has been sourced and
it only happens when completing the command 'cd'. So as a quick
workaround commenting out the following lines in /etc/bash_completion
serves quite well. (And even retains variable name completion for 'cd')

if shopt -q cdable_vars; then
    complete -v -F _cd $nospace $filenames cd
else
    complete -F _cd $nospace $filenames cd
fi

The problem seems to stem that in

COMPREPLY=( $( compgen -v -P '$' -- "${cur#?(\\)$}" ) )

the '$' thats prepended via the option -P gets escaped by bash somehow.
$COMPREPLY has the right value so it has to happen somewhere later.


best regards,
Andreas

Message #19 received at 272660@bugs.debian.org (full text, mbox, reply):

From: Chet Ramey <chet@caleb.ins.cwru.edu>

To: nozone@sbox.tugraz.at

Cc: doko@cs.tu-berlin.de, ian@caliban.org, chet@po.cwru.edu, 272660@bugs.debian.org

Subject: Re: Bug#272660: debugging (forwarded from Andreas Leitner)

Date: Tue, 12 Oct 2004 10:36:59 -0400

> > I did some debugging and have now a vague idea of what goes wrong.
> > The problem only happens once /etc/bash_completion has been sourced and
> > it only happens when completing the command 'cd'. So as a quick
> > workaround commenting out the following lines in /etc/bash_completion
> > serves quite well. (And even retains variable name completion for 'cd')
> > 
> > if shopt -q cdable_vars; then
> >     complete -v -F _cd $nospace $filenames cd
> > else
> >     complete -F _cd $nospace $filenames cd
> > fi
> > 
> > The problem seems to stem that in
> > 
> > COMPREPLY=( $( compgen -v -P '$' -- "${cur#?(\\)$}" ) )
> > 
> > the '$' thats prepended via the option -P gets escaped by bash somehow.
> > $COMPREPLY has the right value so it has to happen somewhere later.
> 
> Yes, the '$' is added later by bash, not by the _cd() shell completion
> function.

I'm not sure what Ian's response means, since the `$' is clearly added
with the -P option.

I don't have all the details, since I don't have a current copy of the
bash completion file, but I'm going to assume that the `$filenames'
above is either -f or `-o filenames'.  That tells readline that you're
completing filenames, and turns on filename-specific post-processing,
which includes quoting shell metacharacters and expansion characters in
the matches.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
						Live...Laugh...Love
Chet Ramey, ITS, CWRU    chet@po.cwru.edu    http://tiswww.tis.cwru.edu/~chet/

Message #24 received at 272660@bugs.debian.org (full text, mbox, reply):

From: Andreas Leitner <nozone@sbox.tugraz.at>

To: chet@po.cwru.edu

Cc: doko@cs.tu-berlin.de, ian@caliban.org, 272660@bugs.debian.org

Subject: Re: Bug#272660: debugging (forwarded from Andreas Leitner)

Date: Tue, 12 Oct 2004 16:58:20 +0200

On Tue, 2004-10-12 at 10:36 -0400, Chet Ramey wrote:
> > > I did some debugging and have now a vague idea of what goes wrong.
> > > The problem only happens once /etc/bash_completion has been sourced and
> > > it only happens when completing the command 'cd'. So as a quick
> > > workaround commenting out the following lines in /etc/bash_completion
> > > serves quite well. (And even retains variable name completion for 'cd')
> > > 
> > > if shopt -q cdable_vars; then
> > >     complete -v -F _cd $nospace $filenames cd
> > > else
> > >     complete -F _cd $nospace $filenames cd
> > > fi
> > > 
> > > The problem seems to stem that in
> > > 
> > > COMPREPLY=( $( compgen -v -P '$' -- "${cur#?(\\)$}" ) )
> > > 
> > > the '$' thats prepended via the option -P gets escaped by bash somehow.
> > > $COMPREPLY has the right value so it has to happen somewhere later.
> > 
> > Yes, the '$' is added later by bash, not by the _cd() shell completion
> > function.
> 
> I'm not sure what Ian's response means, since the `$' is clearly added
> with the -P option.
> 
> I don't have all the details, since I don't have a current copy of the
> bash completion file, but I'm going to assume that the `$filenames'
> above is either -f or `-o filenames'.  That tells readline that you're
> completing filenames, and turns on filename-specific post-processing,
> which includes quoting shell metacharacters and expansion characters in
> the matches.

Yes, $filenames is set to '-o filenames'. Actually I think the '$' _is_
prepended by the _cd() function. Thats what the "-P '$'" in the
"compgen" line stands for. Anyway the problem is not the '$', but the
escaping of it which seems to happen later (after _cd() returns).

regards,
Andreas

Message #29 received at 272660@bugs.debian.org (full text, mbox, reply):

From: Chet Ramey <chet@caleb.ins.cwru.edu>

To: nozone@sbox.tugraz.at

Cc: chet@po.cwru.edu, doko@cs.tu-berlin.de, ian@caliban.org, 272660@bugs.debian.org, chet@po.cwru.edu

Subject: Re: Bug#272660: debugging (forwarded from Andreas Leitner)

Date: Tue, 12 Oct 2004 11:12:57 -0400

> > I don't have all the details, since I don't have a current copy of the
> > bash completion file, but I'm going to assume that the `$filenames'
> > above is either -f or `-o filenames'.  That tells readline that you're
> > completing filenames, and turns on filename-specific post-processing,
> > which includes quoting shell metacharacters and expansion characters in
> > the matches.
> 
> Yes, $filenames is set to '-o filenames'. Actually I think the '$' _is_
> prepended by the _cd() function. Thats what the "-P '$'" in the
> "compgen" line stands for. Anyway the problem is not the '$', but the
> escaping of it which seems to happen later (after _cd() returns).

That's because of the `-o filenames' option, as explained above.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
						Live...Laugh...Love
Chet Ramey, ITS, CWRU    chet@po.cwru.edu    http://tiswww.tis.cwru.edu/~chet/

Message #34 received at 272660@bugs.debian.org (full text, mbox, reply):

From: Andreas Leitner <nozone@sbox.tugraz.at>

To: chet@po.cwru.edu

Cc: doko@cs.tu-berlin.de, ian@caliban.org, 272660@bugs.debian.org

Subject: Re: Bug#272660: debugging (forwarded from Andreas Leitner)

Date: Tue, 12 Oct 2004 17:27:54 +0200

On Tue, 2004-10-12 at 11:12 -0400, Chet Ramey wrote:
> > > I don't have all the details, since I don't have a current copy of the
> > > bash completion file, but I'm going to assume that the `$filenames'
> > > above is either -f or `-o filenames'.  That tells readline that you're
> > > completing filenames, and turns on filename-specific post-processing,
> > > which includes quoting shell metacharacters and expansion characters in
> > > the matches.
> > 
> > Yes, $filenames is set to '-o filenames'. Actually I think the '$' _is_
> > prepended by the _cd() function. Thats what the "-P '$'" in the
> > "compgen" line stands for. Anyway the problem is not the '$', but the
> > escaping of it which seems to happen later (after _cd() returns).
> 
> That's because of the `-o filenames' option, as explained above.

I see. Then I think the fix is easy then. Just drop the "$filenames" as
in:

if shopt -q cdable_vars; then
    complete -v -F _cd $nospace cd
else
    complete -F _cd $nospace cd
fi

But this has the side effect that directories don't get a slash
appended. Another (IMO) cleaner solution would be if there were an
escape sequence for the escaping of the dollar sign. I tried:

 COMPREPLY=( $( compgen -v -P '\$' -- "${cur#?(\\)$}" ) )

But that would then be escaped to '\\\$'. I didn't find anything in the
docs about an escape sequence either for that particular case either...

Andreas

Message #39 received at 272660@bugs.debian.org (full text, mbox, reply):

From: Ian Macdonald <ian@caliban.org>

To: Andreas Leitner <nozone@sbox.tugraz.at>

Cc: chet@po.cwru.edu, doko@cs.tu-berlin.de, ian@caliban.org, 272660@bugs.debian.org

Subject: Re: Bug#272660: debugging (forwarded from Andreas Leitner)

Date: Tue, 12 Oct 2004 10:02:27 -0700

On Tue 12 Oct 2004 at 17:27:54 +0200, you wrote:

> On Tue, 2004-10-12 at 11:12 -0400, Chet Ramey wrote:
> > > > I don't have all the details, since I don't have a current copy of the
> > > > bash completion file, but I'm going to assume that the `$filenames'
> > > > above is either -f or `-o filenames'.  That tells readline that you're
> > > > completing filenames, and turns on filename-specific post-processing,
> > > > which includes quoting shell metacharacters and expansion characters in
> > > > the matches.
> > > 
> > > Yes, $filenames is set to '-o filenames'. Actually I think the '$' _is_
> > > prepended by the _cd() function. Thats what the "-P '$'" in the
> > > "compgen" line stands for. Anyway the problem is not the '$', but the
> > > escaping of it which seems to happen later (after _cd() returns).
> > 
> > That's because of the `-o filenames' option, as explained above.
> 
> I see. Then I think the fix is easy then. Just drop the "$filenames" as
> in:
> 
> if shopt -q cdable_vars; then
>     complete -v -F _cd $nospace cd
> else
>     complete -F _cd $nospace cd
> fi
> 
> But this has the side effect that directories don't get a slash
> appended. Another (IMO) cleaner solution would be if there were an
> escape sequence for the escaping of the dollar sign. I tried:
> 
>  COMPREPLY=( $( compgen -v -P '\$' -- "${cur#?(\\)$}" ) )
> 
> But that would then be escaped to '\\\$'. I didn't find anything in the
> docs about an escape sequence either for that particular case either...

I'm sorry that my original diagnosis was hasty. The fact that I'm no
longer looking at completion code on a daily basis has made me forgetful
of how things work.

This is an example of how it's sometimes difficult to make the options
you want play well together. '-o filenames' is extremely useful and so
you wouldn't really want to turn it off. On the other hand, you want
'-v', too, when you're completing for cd with cdable_vars set, so that
variable names are also returned.

I guess the ideal thing here would be for bash to distinguish between
the completions it had returned due to '-v' and those that it had
returned from '-o filenames'. The latter would have shell metacharacters
escaped, whereas the former would leave the dollar sign alone.

Many of my own completion functions have become a trade-off, due to no
single solution being able to solve all of the detailed problems.
Mostly, if not always, I've chosen to use '-o filenames' and force the
user to deal with escaped metacharacters. The alternative is to have
directories treated incorrectly, which, I think, would be much more
annoying.

Ian
-- 
Ian Macdonald               | Those who are mentally and emotionally
System Administrator        | healthy are those who have learned when to 
ian@caliban.org             | say yes, when to say no and when to say
http://www.caliban.org      | whoopee.   -- W.S. Krabill 
                            | 

Message #44 received at 272660@bugs.debian.org (full text, mbox, reply):

From: Andreas Leitner <nozone@sbox.tugraz.at>

To: Ian Macdonald <ian@caliban.org>

Cc: chet@po.cwru.edu, doko@cs.tu-berlin.de, 272660@bugs.debian.org

Subject: Re: Bug#272660: debugging (forwarded from Andreas Leitner)

Date: Wed, 13 Oct 2004 11:22:45 +0200

On Tue, 2004-10-12 at 10:02 -0700, Ian Macdonald wrote:
> I'm sorry that my original diagnosis was hasty. The fact that I'm no
> longer looking at completion code on a daily basis has made me forgetful
> of how things work.
> 
> This is an example of how it's sometimes difficult to make the options
> you want play well together. '-o filenames' is extremely useful and so
> you wouldn't really want to turn it off. On the other hand, you want
> '-v', too, when you're completing for cd with cdable_vars set, so that
> variable names are also returned.
> 
> I guess the ideal thing here would be for bash to distinguish between
> the completions it had returned due to '-v' and those that it had
> returned from '-o filenames'. The latter would have shell metacharacters
> escaped, whereas the former would leave the dollar sign alone.
> 
> Many of my own completion functions have become a trade-off, due to no
> single solution being able to solve all of the detailed problems.
> Mostly, if not always, I've chosen to use '-o filenames' and force the
> user to deal with escaped metacharacters. The alternative is to have
> directories treated incorrectly, which, I think, would be much more
> annoying.

I see. I got lots of software projects which require their own
environment variable. To change to that project the most simple thing
then is to "cd $PROJECT_NAME". Since I have taken the habit to hitting
TAB all the time (rather subconsciously), this is really annoying. Since
it completes to "cd \$PROJECT_NAME" and I have to go back to the slash
and remove it. I would rather have it not complete at all. I think a
wrong completion is worse than no completion at all.

Anyway, if '-o filenames' would understand an escape sequence and
various completing functions would be aware of it there would be no need
for any compromise, no?

Andreas

Message #59 received at 272660-quiet@bugs.debian.org (full text, mbox, reply):

From: David Paleino <d.paleino@gmail.com>

To: 272660-quiet@bugs.debian.org

Cc: Bash-Completion Developers <bash-completion-devel@lists.alioth.debian.org>, Andreas Leitner <nozone@sbox.tugraz.at>

Subject: Re: bash: completion of env vars broken (leading slash is added)

Date: Sat, 6 Sep 2008 22:46:28 +0200

[Message part 1 (text/plain, inline)]

Hi,
after some years, someone took a look at this bug again ;)

Well, an option would really be using $dirnames (i.e. -o dirnames) instead of
$filenames. But that has drawbacks:

$ cd $H<TAB>
$HISTCMD       $HISTFILE      $HISTSIZE      $HOSTNAME      $HUSHLOGIN
$HISTCONTROL   $HISTFILESIZE  $HOME          $HOSTTYPE      
$ cd $HOM<TAB>
$ cd $HOME

$ cd /tm<TAB>
$ cd /tmp<TAB>
$ cd /tmp

..while one would expect it to be /tmp/, so that the following <TAB> would show
subdirectories... that's what -o filenames (or $filenames, in the file) does:
adding a trailing backslash.

I'm thinking to a way of adding the / to only directories, by not using
$filenames.. someone is working behind the curtains ;)

David

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

[signature.asc (application/pgp-signature, attachment)]

Message #64 received at 272660-quiet@bugs.debian.org (full text, mbox, reply):

From: Morita Sho <morita-pub-en-debian@inz.sakura.ne.jp>

To: David Paleino <d.paleino@gmail.com>

Cc: 272660-quiet@bugs.debian.org, Bash-Completion Developers <bash-completion-devel@lists.alioth.debian.org>, Andreas Leitner <nozone@sbox.tugraz.at>

Subject: Re: bash: completion of env vars broken (leading slash is added)

Date: Sun, 14 Sep 2008 16:27:41 +0900

[Message part 1 (text/plain, inline)]

Hi,

> Well, an option would really be using $dirnames (i.e. -o dirnames) instead of
> $filenames. But that has drawbacks:
> 
> $ cd $H<TAB>
> $HISTCMD       $HISTFILE      $HISTSIZE      $HOSTNAME      $HUSHLOGIN
> $HISTCONTROL   $HISTFILESIZE  $HOME          $HOSTTYPE      
> $ cd $HOM<TAB>
> $ cd $HOME
> 
> $ cd /tm<TAB>
> $ cd /tmp<TAB>
> $ cd /tmp
> 
> ..while one would expect it to be /tmp/, so that the following <TAB> would show
> subdirectories... that's what -o filenames (or $filenames, in the file) does:
> adding a trailing backslash.
> 
> I'm thinking to a way of adding the / to only directories, by not using
> $filenames.. someone is working behind the curtains ;)

I have some ideas to resolve this problem.


1) Remove -o filenames and emulate what -o filenames does in bash-completion,
in fact, add -S "/" option to `compgen -d` and add -S " " to `compgen -f`.

An attached patch emulate_-o_filenames.patch implements this behavior.


2) Or, remove -o filenames and dynamically enable -o filenames flag if needed.
According to the source code of Bash, compgen -f causes to set 1 to
rl_filename_completion_desired, which is Bash's internal variable for -o
filenames flag.
It is undocumented behavior but it works fine for me.

An attached patch enable_-o_filenames_dynamically.patch implements this behavior.


IMO, 2) looks better because 1) has small drawbacks as described below.

With -o filenames enabled:

 $ cd /usr/[TAB]
 X11R6/            i586-mingw32msvc/ lib64/            sbin/
 bin/              include/          libexec/          share/
 games/            lib/              local/            src/

Without -o filenames:

 $ cd /usr/[TAB]
 /usr/X11R6/             /usr/include/           /usr/local/
 /usr/bin/               /usr/lib/               /usr/sbin/
 /usr/games/             /usr/lib64/             /usr/share/
 /usr/i586-mingw32msvc/  /usr/libexec/           /usr/src/

As you can see Bash automatically strips leading /usr/ when -o filenames are
enabled. I think, however, that implement the emulation for this behavior in
bash-completion is impossible.


Thanks,
-- 
Morita Sho <morita-pub-en-debian@inz.sakura.ne.jp>

[emulate_-o_filenames.patch (text/x-patch, inline)]

--- ../bash-completion-20080705/bash_completion	2008-07-05 22:55:03.000000000 +0900
+++ bash_completion	2008-09-12 21:10:42.000000000 +0900
@@ -267,16 +267,22 @@
 
 	_expand || return 0
 
-	local toks=( ) tmp
+	local toks=( ) tmp suffix_opt=( )
+	if [[ "$1" = "-F" || "$2" = "-F" ]]; then
+	  suffix_opt=( -S '/' )
+	fi
 	while read -r tmp; do
 		[[ -n $tmp ]] && toks[${#toks[@]}]=$tmp
-	done < <( compgen -d -- "$(quote_readline "$cur")" )
+	done < <( compgen -d "${suffix_opt[@]}" -- "$(quote_readline "$cur")" )
 	
 	if [[ "$1" != -d ]]; then
+		if [[ "$2" = "-F" ]]; then
+			suffix_opt=( -S ' ' )
+		fi
 		xspec=${1:+"!*.$1"}
 		while read -r tmp; do
 			[[ -n $tmp ]] && toks[${#toks[@]}]=$tmp
-		done < <( compgen -f -X "$xspec" -- "$(quote_readline "$cur")" )
+		done < <( compgen -f "${suffix_opt[@]}" -X "$xspec" -- "$(quote_readline "$cur")" )
 	fi
 
 	COMPREPLY=( "${COMPREPLY[@]}" "${toks[@]}" )
@@ -3128,7 +3134,7 @@
 	# Use standard dir completion if no CDPATH or parameter starts with /,
 	# ./ or ../
 	if [ -z "${CDPATH:-}" ] || [[ "$cur" == ?(.)?(.)/* ]]; then
-		_filedir -d
+		_filedir -d -F
 		return 0
 	fi
 
@@ -3147,7 +3153,7 @@
 		done
 	done
 
-	_filedir -d
+	_filedir -d -F
 
 	if [[ ${#COMPREPLY[@]} -eq 1 ]]; then
 	    i=${COMPREPLY[0]}
@@ -3159,9 +3165,9 @@
 	return 0
 }
 if shopt -q cdable_vars; then
-    complete -v -F _cd $nospace $filenames cd
+    complete -v -F _cd $nospace cd
 else
-    complete -F _cd $nospace $filenames cd
+    complete -F _cd $nospace cd
 fi
 
 _remove_comp_word()

[enable_-o_filenames_dynamically.patch (text/x-patch, inline)]

--- ../bash-completion-20080705/bash_completion	2008-07-05 22:55:03.000000000 +0900
+++ bash_completion	2008-09-12 21:40:06.000000000 +0900
@@ -3125,6 +3125,9 @@
 		return 0
 	fi
 
+	# Enable -o filenames option
+	compgen -f /non-existing-dir/ > /dev/null
+
 	# Use standard dir completion if no CDPATH or parameter starts with /,
 	# ./ or ../
 	if [ -z "${CDPATH:-}" ] || [[ "$cur" == ?(.)?(.)/* ]]; then
@@ -3159,9 +3162,9 @@
 	return 0
 }
 if shopt -q cdable_vars; then
-    complete -v -F _cd $nospace $filenames cd
+    complete -v -F _cd $nospace cd
 else
-    complete -F _cd $nospace $filenames cd
+    complete -F _cd $nospace cd
 fi
 
 _remove_comp_word()

Message #71 received at 272660-close@bugs.debian.org (full text, mbox, reply):

From: David Paleino <d.paleino@gmail.com>

To: 272660-close@bugs.debian.org

Subject: Bug#272660: fixed in bash-completion 1:1.0-1

Date: Sat, 04 Apr 2009 13:47:04 +0000

Source: bash-completion
Source-Version: 1:1.0-1

We believe that the bug you reported is fixed in the latest version of
bash-completion, which is due to be installed in the Debian FTP archive:

bash-completion_1.0-1.diff.gz
  to pool/main/b/bash-completion/bash-completion_1.0-1.diff.gz
bash-completion_1.0-1.dsc
  to pool/main/b/bash-completion/bash-completion_1.0-1.dsc
bash-completion_1.0-1_all.deb
  to pool/main/b/bash-completion/bash-completion_1.0-1_all.deb
bash-completion_1.0.orig.tar.gz
  to pool/main/b/bash-completion/bash-completion_1.0.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 272660@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Paleino <d.paleino@gmail.com> (supplier of updated bash-completion package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 03 Apr 2009 14:21:43 +0200
Source: bash-completion
Binary: bash-completion
Architecture: source all
Version: 1:1.0-1
Distribution: unstable
Urgency: low
Maintainer: Bash Completion Maintainers <bash-completion-devel@lists.alioth.debian.org>
Changed-By: David Paleino <d.paleino@gmail.com>
Description: 
 bash-completion - programmable completion for the bash shell
Closes: 272660 322238 360628 361535 489927 491856 492328 492476 494292 495142 495883 496162 496828 497074 497597 498105 499780 500316 501473 501843 502664 502804 502885 503317 503317 504141 504547 504650 506560 511789 511790 512556 512823 512917 516614 521041
Changes: 
 bash-completion (1:1.0-1) unstable; urgency=low
 .
   * New upstream release:
     - also see /usr/share/doc/bash-completion/CHANGES.gz
     - fix man -l completing filenames (Closes: #497074)
     - (Partly) fixed java classes completion (Closes: #496828). Look for
       FIXME in source.
     - dump to /dev/null error message from look(1) with no arguments
       (Closes: #495142)
     - set ssh as default for rsync (was rsh) (Closes: #492328)
     - added .oga, .ogv, .ogx to mplayer completion (Closes: #496162)
     - added .epub to unzip|zipinfo completion (Closes: #492476)
     - added ssh-copy-id completion (Closes: #491856)
     - moved ssh completion to separate file (Closes: #360628)
     - bogus completion when mounting subdirs fixed (Closes: #322238)
     - fix `apt-cache showsrc` completing only on source package names
       (Closes: #361535)
     - fixed bugs with gdb completion:
     - when an empty directory is in $PATH (thanks to Morita Sho)
       (Closes: #497597)
     - when a non-existing directory is in $PATH (Closes: #499780)
     - fix missing completion for "-n" and "-e" (we were using echo, now
       using printf) (thanks to Morita Sho) (Closes: #498105)
     - fixed gpg completion --@(export|@(?(l|nr|nrl)sign|edit)-key))
       (Closes: #500316)
     - fixed .cb[rz] completion for evince (Closes: #502885)
     - added gpg2 completion (Closes: #489927)
     - fixed mplayer -skin completion (Closes: #501473)
     - fixed errors with POSIX enabled (Closes: #502804)
     - fixed dpkg-source wrong exit() with return() (Closes: #503317)
     - added --schedule-only to aptitude's completion (Closes: #502664)
     - added build-dep to aptitude's completion (Closes: #495883)
     - added support for `-F configfile' to _known_hosts(), ssh, scp and
       sftp, thanks to Freddy Vulto (Closes: #504141)
     - fixed sed quoting bug in _known_hosts(), thanks to Freddy Vulto
       (Closes: #504650)
     - allow for comments in known_hosts files (Closes: #511789)
     - fixed perl -I/-x completion, thanks to Freddy Vulto
       (Closes: #504547)
     - README updated: explain how to use bash-completion correctly.
       (Closes: #506560)
     - added qdbus completion, thanks to Terence Simpson (LP: #257903)
     - fixed completion of environment variables, thanks to Morita Sho
       (Closes: #272660)
     - fix dpkg completion bug: it listed only non-Essential packages
       (Closes: #511790)
     - fixed _dpkg_source completion (Closes: #503317)
     - remove unused UNAME local variable in _info() (Closes: #501843)
     - added .zip to jar completions (Closes: #521041)
     - Merge from Ubuntu:
       + consume error messages in configure completion (LP: #223882)
         (Mika Fischer)
       + quote $xspec in _filedir_xspec in case it is empty, which would
         cause errors if there was no match under failglob. (LP: #194419)
         (Mika Fischer)
     - Ville Skyttä:
       + remove duplicate cpio completion, thanks to Freddy Vulto
         (Closes: #512823)
       + fix awk error in "modprobe -r /" completion (Closes: #512556)
     - Jakob Unterwurzacher:
       + ps2pdf can run on .pdf files as well.
         (Closes: #516614, LP: #316943)
   * debian/links fixed (Closes: #494292)
   * debian/control:
     - fixed typo in the long description
     - added Vcs-* fields
     - Standards-Version to 3.8.1
     - DMUA set
     - removed Luk Claes from Uploaders
     - Homepage added
   * debian/install:
     - correctly install contrib/* under /etc/bash_completion.d/
   * debian/copyright updated
   * debian/extra/dh_bash-completion:
     - updated to support a list of files in debian/<package>.bash-completion
       (Closes: #512917)
   * debian/rules:
     - install upstream CHANGES and AUTHORS too
Checksums-Sha1: 
 977d1414ca3556a4ad46aa2b48b9ca8e6e86a603 1308 bash-completion_1.0-1.dsc
 61040795731f5ff509c46e818a1edf0a7a93e11d 143578 bash-completion_1.0.orig.tar.gz
 49c583802082e3aa9a761fb0da0d5ec257f257bb 9002 bash-completion_1.0-1.diff.gz
 cb38e807d9b23e84b866e6e9d24814991a61836a 103010 bash-completion_1.0-1_all.deb
Checksums-Sha256: 
 d369f9436c02262d3de898564cd9b5269ace760cf6b7e0632e3b251ac431f2b5 1308 bash-completion_1.0-1.dsc
 bd96e7d2858f02783046908a984993736f1189d07d82e9ce4b465068dd7187ef 143578 bash-completion_1.0.orig.tar.gz
 04c46eff31bf9dfb9e79f417bd79706b6dc67888461ab05128b29cff78c9556b 9002 bash-completion_1.0-1.diff.gz
 81ab4b27a2158e787ea39c7da34619858a5df6b6251ba24d8bda6592feed46f4 103010 bash-completion_1.0-1_all.deb
Files: 
 6cb01d355c4519f911820b2b7c0feb53 1308 shells standard bash-completion_1.0-1.dsc
 cd1c5648272917fbe0eef4ba30bb93f4 143578 shells standard bash-completion_1.0.orig.tar.gz
 e78d5e31ed66fb5e97c77ea7c9f1b343 9002 shells standard bash-completion_1.0-1.diff.gz
 aefc9e1c8db0f4f2b61557c2e207ca0c 103010 shells standard bash-completion_1.0-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknXYZAACgkQ5UTeB5t8Mo0jGACfQVygJmdQ3v4i/dymRnZSVnhA
qHoAnjcS99HMQgFHzQ2NnNAY1OPvlPK6
=6i7t
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.