Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 77115

Summary:	Wrong file globbing behavior
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <jan.gruenwald>
Component:	bash	Assignee:	Tim Waugh <twaugh>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	8.0	CC:	mitr
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-11-01 23:52:59 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 Need Real Name 2002-11-01 11:21:46 UTC

Description of Problem:

If I do a

   $ ls [a-z]*

to get all filename beginning with a lowercase letter it also shows
files beginning with uppercase letters

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

[jan@torgau jan]$ bash --version
GNU bash, version 2.05b.0(1)-release (i686-pc-linux-gnu)
Copyright (C) 2002 Free Software Foundation, Inc.


How Reproducible:


Steps to Reproduce:
1. ls [a-z]*
2. 
3. 

Actual Results:
s.a.

Expected Results:
s.a.

Additional Information:

Comment 1 Need Real Name 2002-11-01 15:11:50 UTC

I just checked it as "root" user.
There it works as expected.

Comment 2 giulioo 2002-11-01 16:06:26 UTC

I think this is expected behavior.
Try setting LC_COLLATE=C and then retry.

Comment 3 Need Real Name 2002-11-01 18:59:48 UTC

The "LC_COLLATE=C" didn't change anything

Comment 4 Miloslav Trmac 2002-11-01 23:52:53 UTC

You'll need to use bash-2.05-7 from rawhide for changes to have
immediate effect.
To see the result without upgrading, do
LC_COLLATE=C bash -c 'ls [a-z]*'

Comment 5 Tim Waugh 2002-11-02 16:27:53 UTC


*** This bug has been marked as a duplicate of 74701 ***

Comment 6 Tim Waugh 2002-11-05 14:00:18 UTC

*** Bug 77339 has been marked as a duplicate of this bug. ***