[Bash-completion-devel] Bug#739835: ~ vs. filename expansion

2014-03-11 Thread Matthew Gabeler-Lee
Package: bash-completion Version: 1:2.1-2 Followup-For: Bug #739835 Dear Maintainer, Now that jessie has upgrade to bash 4.3, this is pretty much making bash-completion unusable! The patch referenced JuanJo Ciarlante definitely fixes the problem for me. -- System Information: Debian Release: j

[Bash-completion-devel] Bug#739835: ~ vs. filename expansion

2014-03-11 Thread JuanJo Ciarlante
Following patch (from this MP[1]) seems to fix it for me - at least for: 1) completion when 1st char is '~' 2) fixing potential double escaping when the argument is already escaped, eg: cat /tmp/file\ with\ spac revno: 46 committer: Jua

[Bash-completion-devel] Bug#741273: Bug#741273: bash-completion BROKEN with 'nounset'

2014-03-11 Thread Ville Skyttä
On Mon, Mar 10, 2014 at 6:41 PM, Paul Nienaber wrote: > Debian's bash-completion (not upstream) is broken when 'nounset' is set. It's not a Debian-only issue, upstream bash-completion is broken in that setup too. And this is a known one, tracked and discussed at https://alioth.debian.org/tracker/