Bug 1296366

Summary: Bash completion for more(1) handles file names with spaces incorrectly
Product: Red Hat Enterprise Linux 7 Reporter: Frank Zdarsky <fzdarsky>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: Leos Pol <lpol>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.2CC: J.H.Hodrien, lpol, todoleza, zpytela
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 21:26:03 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:

Description Frank Zdarsky 2016-01-07 01:14:08 UTC 
Description of problem:
When using bash completion for more(1) on a file whose name contains spaces, parts before and after the spaces are interpreted as different files.

Version-Release number of selected component (if applicable):
util-linux.x86_64                2.23.2-26.el7 

How reproducible:
always

Steps to Reproduce:
1. in an empty directory type
$ touch foo\ bar
$ more foo<tab>

Actual results:
Bash completion offers the choice between two files:
$ more foo<tab>
bar  foo

Expected results:
The command line is completed to:
$ more foo\ bar
Comment 3 Mike McCune 2016-03-28 22:54:17 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
Comment 6 Karel Zak 2016-07-07 10:30:18 UTC 
*** Bug 1352096 has been marked as a duplicate of this bug. ***
Comment 7 Leos Pol 2016-09-27 07:03:23 UTC 
# rpm -q util-linux
util-linux-2.23.2-26.el7.x86_64
# touch foo\ bar
# more f
bar  foo  

# rpm -q util-linux
util-linux-2.23.2-33.el7.x86_64
# more foo\ bar
Comment 9 errata-xmlrpc 2016-11-03 21:26:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2605.html