Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 177250 - Bash completion mishandles colon characters
Bash completion mishandles colon characters
Product: Fedora
Classification: Fedora
Component: bash (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2006-01-08 03:15 EST by JW
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-09 04:10:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description JW 2006-01-08 03:15:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; MSIE 6.0; Windows; U; AIIEEEE!; Win98; Windows 98; en-US; Gecko masquerading as IE; should it matter?; rv:1.8b) Gecko/20050217

Description of problem:
For some reason bash treats a colon in a filename in a different way to other charcters, even though it is neither a glob'able, directory separator, or in any other way a special character (except in certain contexts such as variable expansion etc).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. cd /some-directory-containing-many-files
2. touch a:b
3. ls a:<TAB> OR ls a:<CTRL-D>

Actual Results:  Display all 654 possibilities? (y or n)

Expected Results:  Display all 1 possibilities? (y or n)

Additional info:

You must have filename-completion enabled in bash (see your ~/.inputrc or /etc/inputrc).
Comment 1 Tim Waugh 2006-01-08 05:58:15 EST
This behaviour is intentional, for convenience when setting PATH-like variables.
Comment 2 Tim Waugh 2006-01-08 05:58:48 EST
(Of course, you can escape it: ls a\:<TAB>)
Comment 3 JW 2006-01-08 08:01:57 EST
How strange ... "... for convenience when setting PATH-like variables".
Let's think this through carefully.
There you are, at a shell prompt, setting your PATH, using filename-completion.

I wonder how often people do that, compared to the number of times a filename
has a colon in it! LOL!

Comment 4 Tim Waugh 2006-01-09 04:10:01 EST
This is intentional behaviour.

Note You need to log in before you can comment on or make changes to this bug.