Bug 221428 - bash file completion screwed up with somefile:
bash file completion screwed up with somefile:
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: bash (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-04 12:02 EST by Horst H. von Brand
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:
Environment:
Last Closed: 2007-01-04 12:12:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
My .bash_profile (767 bytes, text/plain)
2007-01-04 12:02 EST, Horst H. von Brand
no flags Details
My .bashrc (980 bytes, text/plain)
2007-01-04 12:03 EST, Horst H. von Brand
no flags Details

  None (edit)
Description Horst H. von Brand 2007-01-04 12:02:32 EST
Description of problem:
Filenames containing : are completed weirdly

Version-Release number of selected component (if applicable):
bash-3.2-1.fc7

How reproducible:
Always

Steps to Reproduce:
1. ls /etc/gdm/custom.conf:<TAB>
2.
3.
  
Actual results:
ls /etc/gdm/custom.conf:/etc/gdm/custom.conf\:0

Expected results:
ls /etc/gdm/custom.conf\:0

Additional info:
This happens with my (bog standard) .bash_profile and .bashrc (attached), but
not when I run "bash --noprofile --norc" (?)
Comment 1 Horst H. von Brand 2007-01-04 12:02:32 EST
Created attachment 144817 [details]
My .bash_profile
Comment 2 Horst H. von Brand 2007-01-04 12:03:14 EST
Created attachment 144818 [details]
My .bashrc
Comment 3 Tim Waugh 2007-01-04 12:04:17 EST
What does 'echo $COMP_WORDBREAKS' say?
Comment 4 Horst H. von Brand 2007-01-04 12:09:37 EST
$ echo $COMP_WORDBREAKS
"'><=;|&(:
Comment 5 Horst H. von Brand 2007-01-04 12:10:42 EST
BTW, I've also got bash-completion-20060301-2.fc6
Comment 6 Tim Waugh 2007-01-04 12:12:54 EST
Working as expected.  ':' is in the default COMP_WORDBREAKS so that
auto-completion works correctly when building a PATH-style variable on the
command line, for example.  Set COMP_WORDBREAKS differently if you like, or use
'\:' instead of ':' to use a literal ':' character in a filename and have
completion work.

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