Closed Bug 187945 Opened 23 years ago Closed 10 years ago

file: doesn't respect $LC_COLLATE

Categories

(Core :: Networking: File, enhancement)

x86
Linux
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: jmd, Assigned: steveh)

References

Details

% touch foo.doc % touch foo-revA.doc % export LC_COLLATE=en_US.UTF-8 Now open that directory with file: foo.doc should be listed before foo-revA.doc, like with "ls". It's not. See also bug 20009.
Can you put the "ls" output in here as well?
% mkdir tmp % cd tmp % touch foo.doc % touch foo-revA.doc % LC_COLLATE=C ls -l total 0 -rw-r--r-- 1 jmd jmd 0 Jan 6 15:15 foo-revA.doc -rw-r--r-- 1 jmd jmd 0 Jan 6 15:15 foo.doc % LC_COLLATE=en_US.UTF-8 ls -l total 0 -rw-r--r-- 1 jmd jmd 0 Jan 6 15:15 foo.doc -rw-r--r-- 1 jmd jmd 0 Jan 6 15:15 foo-revA.doc %
FWIW, I do not see the desired behavior with my ls. --->ls --version ls (fileutils) 4.1 Written by Richard Stallman and David MacKenzie. Copyright (C) 2001 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I am not sure why this is important or why I would want to fix this - moving out. Please kick me if this is required by someone.
Severity: normal → enhancement
Target Milestone: --- → Future
*** Bug 209695 has been marked as a duplicate of this bug. ***
Not sure if this is the same as the bug 209695 I reported, but if it is, it's certainly more important than the "why would I want to fix it?" comment suggests. It's pretty annoying and confusing to users to have files in the Open File dialog listed in the wrong order. Please see my submission and re-visit this issue. Thanks very much.
Steve, dougt is just prioritizing his work. This is a collaborative effort... you're welcome to fix this yourself, otherwise it will probably remain in the "future" state indefinitely.
Assignee: dougt → steveh
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.