Bug 1018980 - Bash completion for man is too aggressive
Bash completion for man is too aggressive
Product: Fedora
Classification: Fedora
Component: bash-completion (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-10-14 16:26 EDT by Pete Zaitcev
Modified: 2013-10-14 17:31 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-14 17:31:23 EDT
Type: Bug
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 Pete Zaitcev 2013-10-14 16:26:48 EDT
Description of problem:

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

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


How reproducible:


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:


Additional info:
Comment 1 Ville Skyttä 2013-10-14 17:06:14 EDT
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 17:31:23 EDT
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.