[Bash-completion-devel] Bug#825317: bash-completion: Un-escaped "~*" leads to spurious NSS lookups

Since Debian is about to release, and this is an easy fix, shouldn’t we get this into testing ASAP? It’s really annoying how much larger this bug makes log files for a false positive. The fix has been listed for over a year, can it get added or is it still being tested?

[Bash-completion-devel] Bug#833059:

I'm on Wheezy with bash-completion version 2.1-4 and I can confirm. I believe I have also narrowed the bug down. This lists files in root: $ du --exclude=asdf / But this (with quotes) does not: $ du --exclude="asdf" / After a quick survey, it seems like it happens to all options that have an

[Bash-completion-devel] Bug#788346:

I am on Wheezy right now and can confirm this behavior (same version of the package). "/bin/sh" links to "/bin/dash", which also completes non-.sh files like bash. I think both "/bin/sh" and "/bin/dash" should have the same completion behavior because they're the same executable. I'd imagine the

[Bash-completion-devel] Bug#843492: Bug#843492:

On Fri, Jun 9, 2017 at 10:30 AM, Aditya Vaidya wrote: > Is this a duplicate of bug #799545 ? Yes. ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org

[Bash-completion-devel] Bug#843492:

Is this a duplicate of bug #799545 ? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799545 Sincerely, Aditya Vaidya ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org