RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 994493 - cli: improve bash completion
Summary: cli: improve bash completion
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks: 980210
TreeView+ depends on / blocked
 
Reported: 2013-08-07 11:51 UTC by Tomas Dolezal
Modified: 2014-06-18 03:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:34:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Dolezal 2013-08-07 11:51:09 UTC
Description of problem:
bash completion: automatic completion does not work until one or two leading dashes are entered before tapping <tab>.
Also, if user specify e.g. `firwall-cmd --add-service=http <tab>` only --timeout is completed. After that completion finishes. -> What if user wants to specify permanent instead of --timeout? Of course it is possible by prepending it to --add-service, but that is not much friendly.

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

How reproducible:
always

Steps to Reproduce:
firewall-cmd --add-service=http <tab>

Actual results:
completion: firewall-cmd --add-service=http --timeout=

Expected results:
completion: firewall-cmd --add-service=http <tab><tab>
            --permament --timeout --zone (and maybe other options)

please fix or provide information why do you think it shouldn't be fixed this way
thanks

Additional info:
CCed affiliated users

Comment 2 Jiri Popelka 2013-09-20 14:32:37 UTC
(In reply to Tomas Dolezal from comment #0)
> bash completion: automatic completion does not work until one or two leading
> dashes are entered before tapping <tab>.

It's the same with iptables tool, i.e. one needs to add a leading dash before <tab> starts to work.

> Also, if user specify e.g. `firwall-cmd --add-service=http <tab>` only
> --timeout is completed. After that completion finishes. -> What if user
> wants to specify permanent instead of --timeout? Of course it is possible by
> prepending it to --add-service, but that is not much friendly.

Fixed upstream:
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=813a9abf57c68416e51be7b6f24d16cdf82ab191

Comment 9 Ludek Smid 2014-06-13 12:34:36 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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