Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#39086 - [bash-completion] tab completion of file names starting with '[' files for bash-4.3

Attached to Project: Arch Linux
Opened by Allan McRae (Allan) - Saturday, 01 March 2014, 03:39 GMT
Last edited by Eric Belanger (Snowman) - Thursday, 20 March 2014, 04:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Do:

touch '[foobar]'
rm \[<tab>

and notice the lack of anything occurring.
This task depends upon

Closed by  Eric Belanger (Snowman)
Thursday, 20 March 2014, 04:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  bash-completion 2.1-3
Comment by Gustavo Alvarez (sl1pkn07) - Saturday, 01 March 2014, 09:18 GMT
i have same issue

"ls \[" only show folders, no files
Comment by Matthias Dienstbier (fs4000) - Saturday, 01 March 2014, 22:30 GMT
Probably related: I noticed that "~/" also only suggests folders but no files or anything else.
Comment by Gustavo Alvarez (sl1pkn07) - Sunday, 02 March 2014, 01:24 GMT
downgrading bash from [testing] to [core]), my error is gone

greetings
Comment by Allan McRae (Allan) - Sunday, 02 March 2014, 01:26 GMT
Just to be clear, uninstalling bash-completion makes file name tab completion in bash work again. This is a bash-completion issue.
Comment by Dave Reisner (falconindy) - Sunday, 02 March 2014, 02:36 GMT
-- At least for the homedir expansion problem, the problem boils down to the difference in quoting

$ bash42 -c "printf '%q\n' '~/.'"
~/.

$ bash43 -c "printf '%q\n' '~/.'"
\~/.

This is a bugfix in bash 4.3. I guess bash_completion needs to deal with this somehow in _quote_readline_by_ref

The square brace expansion issue is a little more confusing to me, but I've been able to reduce it down to the difference between the result of:

$ compgen -f -X '' -- \\\[

Assuming that a file such as '[foo' exists. Oddly, in bash 4.3, this will yield a match, whereas in bash 4.2, it will not. This seems more like it might be a bug in bash, not bash_completion.
Comment by Gustavo Alvarez (sl1pkn07) - Monday, 17 March 2014, 18:30 GMT
EDIT: nevermind (i have a bad day)

bash-completion 2.1-3 works

Loading...