Bug 77115 - Wrong file globbing behavior
Wrong file globbing behavior
Status: CLOSED DUPLICATE of bug 74701
Product: Red Hat Linux
Classification: Retired
Component: bash (Show other bugs)
8.0
i686 Linux
high Severity high
: ---
: ---
Assigned To: Tim Waugh
:
: 77339 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-01 06:21 EST by Need Real Name
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-11-01 18:52:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-11-01 06:21:46 EST
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 10:11:50 EST
I just checked it as "root" user.
There it works as expected.
Comment 2 giulioo 2002-11-01 11:06:26 EST
I think this is expected behavior.
Try setting LC_COLLATE=C and then retry.


Comment 3 Need Real Name 2002-11-01 13:59:48 EST
The "LC_COLLATE=C" didn't change anything
Comment 4 Miloslav Trmac 2002-11-01 18:52:53 EST
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 11:27:53 EST

*** This bug has been marked as a duplicate of 74701 ***
Comment 6 Tim Waugh 2002-11-05 09:00:18 EST
*** Bug 77339 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.