Bug 1053570

Summary:	bash completion of $HOME/ to \$HOME/ (with backslash)
Product:	[Fedora] Fedora	Reporter:	dhardy <redhat>
Component:	bash-completion	Assignee:	Ville Skyttä <ville.skytta>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	fb.bugs.rh, ovasik, rrakus, sheltren, ville.skytta
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 10:52:57 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:

Description dhardy 2014-01-15 12:40:32 UTC

Hello,

I originally reported this on the GNU bug-bash mailing list, but was told I should forward the issue.

----------------
The problem:

If I enter

$ ls $HOME/Do

and press the Tab key, bash expands to

$ ls \$HOME/Documents

(notice $ is replaced with \$). This is from my point of view an annoying 
anti-feature, since I must then remove the escaping back-slash.

----------------
Response on GNU's bug-bash list (copied from
http://lists.gnu.org/archive/html/bug-bash/2014-01/msg00064.html ):

This is a problem with bash_completion.  Patch 29 to bash-4.2 fixed this
problem for the default (non-bash-completion) case.  If you remove the
completion specifications (complete -r), the backslash doesn't get added.
You can't just delete the completion specification for ls, since Fedora
has a default completion that installs a new completion for ls the next
time completion is attempted.  I don't know what the problem is with
bash_completion, but you should probably file a bug report with Fedora.

You can set the `direxpand' option and probably get around most of this,
with the change that variables will be expanded upon completion, as in
bash-4.1.

Chet

---------------
My system: Fedora 20,
GNU bash, version 4.2.45(1)-release (x86_64-redhat-linux-gnu)

Comment 1 Fedora End Of Life 2015-05-29 10:30:45 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2 Fedora End Of Life 2016-07-19 10:52:57 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.