Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1983092

Summary: Unexpected behaviour of default tab completion
Product: Red Hat Enterprise Linux 8 Reporter: Paulo Andrade <pandrade>
Component: bash-completionAssignee: Siteshwar Vashisht <svashisht>
Status: CLOSED MIGRATED QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: low    
Version: 8.4CC: abjoshi, amepatil, amkulkar, jcastran
Target Milestone: betaKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2225355 (view as bug list) Environment:
Last Closed: 2023-09-20 19:33:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2225355    

Description Paulo Andrade 2021-07-16 13:48:28 UTC
Sample reproducer environment:

"""
# cat > input.file<<EOF
a
b
c
d
EOF

# for i in $(cat input.<TAB>
"""

  In rhel 7 it would correct complete 'input.file'.

  In rhel 8 it just bells and does not auto complete. It works if adding a backslash before the dollar sign, for example:

# for i in \$(cat input.<TAB>

or if adding a newline:

# for f in
$(cat input.<TAB>

  The easiest workaround is to not let it generate an autocompletion for 'for', and have in .bashrc or similar file the command:

complete -o default for

but this is just working around what appears to be a bug, as when spawning the subshell to generate the auto completion, it is actually attempting to autocomplete the string '$(cat input.' instead of 'input.'

Another possible workaround, but really brute force would be to have:

shopt -u progcomp

in some initialization file, but that would not really bring compatibility with rhel7 behavior. Still, it would work usages of:

$(cat input.

other than just as a 'for' argument.

Comment 1 Siteshwar Vashisht 2021-10-14 10:27:56 UTC
*** Bug 1982830 has been marked as a duplicate of this bug. ***

Comment 3 Siteshwar Vashisht 2021-10-15 09:09:54 UTC
https://github.com/scop/bash-completion/issues/630

Comment 10 RHEL Program Management 2023-09-20 19:31:58 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 11 RHEL Program Management 2023-09-20 19:33:48 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.