Bug 221428 - bash file completion screwed up with somefile:
Summary: bash file completion screwed up with somefile:
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: bash
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-01-04 17:02 UTC by Horst H. von Brand
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-01-04 17:12:54 UTC
Type: ---
Embargoed:


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

Description Horst H. von Brand 2007-01-04 17:02:32 UTC
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 17:02:32 UTC
Created attachment 144817 [details]
My .bash_profile

Comment 2 Horst H. von Brand 2007-01-04 17:03:14 UTC
Created attachment 144818 [details]
My .bashrc

Comment 3 Tim Waugh 2007-01-04 17:04:17 UTC
What does 'echo $COMP_WORDBREAKS' say?

Comment 4 Horst H. von Brand 2007-01-04 17:09:37 UTC
$ echo $COMP_WORDBREAKS
"'><=;|&(:


Comment 5 Horst H. von Brand 2007-01-04 17:10:42 UTC
BTW, I've also got bash-completion-20060301-2.fc6

Comment 6 Tim Waugh 2007-01-04 17:12:54 UTC
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.