Bug 1722727

Summary:	Append '/' while tab completing directory names with bash-completion
Product:	[Fedora] Fedora	Reporter:	kyoneyama <kyoneyam>
Component:	bash-completion	Assignee:	Siteshwar Vashisht <svashisht>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	30	CC:	ddu, kdudka, kyoneyam, mrunge, ooprala, sheltren, svashisht
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1504523	Environment:
Last Closed:	2020-05-26 18:22:45 UTC	Type:	---
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:	1504523, 1505938
Bug Blocks:

Description kyoneyama 2019-06-21 06:32:29 UTC

+++ This bug was initially created as a clone of Bug #1504523 +++

Description of problem:

In bash-4.3, when use tab to auto complete the variable, if the variable is
a directory, it will attend a "/" after the variable.

# ls $HOM    -> click TAB
# ls $HOME/

RHEL provides bash-4.2 in RHEL7, it will attend a space after the variable.

# ls $HOM    -> click TAB
# ls $HOME<space>

In #1495398 a test patch has been created which can achieve this function in bash-4.2

But when bash-completion is installed, it will change the behavior.

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

bash-completion-2.1-6.el7

How reproducible:

everytime

Steps to Reproduce:

# ls $HOM    -> click TAB
# ls $HOME<space>

Actual results:

# ls $HOME<space>

Expected results:

# ls $HOME/

Additional info:

"shopt -u progcomp" will do the job but it will disable auto-completion well.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2017-10-20 06:06:06 UTC ---

Since this bug report was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Siteshwar Vashisht on 2017-10-24 14:17:22 UTC ---

It is still not supported by upstream, so it needs to be implemented in upstream first before it is backported to RHEL.

--- Additional comment from Siteshwar Vashisht on 2018-01-04 10:14:11 UTC ---

Upstream issue: https://github.com/scop/bash-completion/issues/171

--- Additional comment from kyoneyama on 2019-05-29 10:58:18 UTC ---

Hello,

The same bug#1505938 for fedora28 has been closed due to EOL.
What is the plan for fixing this bug?

--- Additional comment from kyoneyama on 2019-06-06 07:36:36 UTC ---

Hello, 

How is the progress on this ?

Comment 2 Ben Cotton 2020-04-30 20:23:59 UTC

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2020-05-26 18:22:45 UTC

Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.