Bug 1018980 - Bash completion for man is too aggressive
Summary: Bash completion for man is too aggressive
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: bash-completion
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ville Skyttä
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 20:26 UTC by Pete Zaitcev
Modified: 2013-10-14 21:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-14 21:31:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Pete Zaitcev 2013-10-14 20:26:48 UTC 
Description of problem:

When developing a man page, man -l something.1 cannot be completed.

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

bash-completion-2.1-2.fc19.noarch

How reproducible:

100%

Steps to Reproduce:
1. git clone git://github.com/openstack/python-swiftclient.git python-swiftclient
2. cd python-swiftclient
3. man -l doc/mangages/<TAB>

Actual results:

No completion

Expected results:

Completion

Additional info:
Comment 1 Ville Skyttä 2013-10-14 21:06:14 UTC 
Works fine for me.

Do "set -x" in a shell, invoke the completion that doesn't work as you expected, and attach the output here after reviewing that it doesn't contain anything you don't want to attach here.

Also, what does "complete -p man" output before and after invoking the man completion?
Comment 2 Pete Zaitcev 2013-10-14 21:31:23 UTC 
Oh, never mind, I see what happened. I typed "man -m doc/manpages/<TAB>".
But the -m option was erroneous. I meant -l.
Note You need to log in before you can comment on or make changes to this bug.