Bug 67106

Summary:	file list expansions using [M-N] ranges produces wrong results
Product:	[Retired] Red Hat Raw Hide	Reporter:	ellson
Component:	bash	Assignee:	wdovlrrw <brosenkr>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-06-20 14:16:00 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:

Description ellson 2002-06-20 03:23:23 UTC

Description of Problem:
"ls [M-N]" should list only file "M" and "N" if they exist, not "m" or "n"


Version-Release number of selected component (if applicable):
bash-2.05a-14.i386.rpm

How Reproducible:
100%

Steps to Reproduce:
1. touch m M n
2. ls [M-N]
3. 

Actual Results:
M n

Expected Results:
M

Additional Information:
Problem does not exist in bash-2.05a-13 from Redhat-7.3

Comment 1 Bernhard Rosenkraenzer 2002-06-20 11:30:31 UTC

This is the correct result.
Bash is i18n aware these days.
If you don't like it, use LC_COLLATE=C

Comment 2 ellson 2002-06-20 11:59:50 UTC

I think that LC_COLLATE=C should be the default so that the behavior of
shell scripts and Makefiles don't suddenly change.

Comment 3 ellson 2002-06-20 14:15:54 UTC

LC_COLLATE=C does restore reasonable behavior, but 
I can't see the logic of the new changed collate sequence.  It still looks like
a bug to me.

In the example:
   touch m M n 
   ls [M-N]
why is "M" listed but not "m"