Opened 13 years ago
Closed 13 years ago
#8071 closed bug (fixed)
ls bug compairing filenames with certain chars
Reported by: | ribbonz | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/Command Line Tools | Version: | R1/alpha3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
This is probably just an ls bug, but I'm adding a ticket just in case.
Here's the output from Terminal that gives a simple way to produce the error:
~> mkdir tmp
~> cd tmp
~/tmp> touch 'Efigênia'
~/tmp> ll
total 2
-rw-r--r-- 1 user root 0 Oct 30 12:50 Efigênia
~/tmp> touch abc
~/tmp> ll
ls: cannot compare file names 'Efig\303\252nia' and 'abc': Invalid Argument
total 4
-rw-r--r-- 1 user root 0 Oct 30 12:50 Efigênia
-rw-r--r-- 1 user root 0 Oct 30 12:51 abc
~/tmp> ls --version
ls (GNU coreutils) 8.4
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Richard M. Stallman and David MacKenzie.
~/tmp> uname -a
Haiku shredder 1 42211 Jun 18 2011 08:26:42 BePC Haiku
~/tmp>
The "cannot compare file names..." error message came up after I had downloaded a jpeg file that had 'Efigênia' as part of the name.
I'm using a stock alpha3. I don't know if coreutils has been updated since then (I'm guessing not).
Change History (4)
comment:1 by , 13 years ago
Component: | - General → Applications/Command Line Tools |
---|
comment:2 by , 13 years ago
What locale? Um... the regular one, I guess. I haven't changed anything.
Preferences::Locale app shows "English" in the Language tab, and "English (United States)" in the Formatting tab. Which works for me, because I speak English and live in the United States. :)
comment:3 by , 13 years ago
comment:4 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This is indeed a bug in ls ; if the locale isn't set, it defaults to the POSIX locale and doesn't correctly handle anything non-ascii. This doesn't occur on newer revisions though since we now explicitly set the LC_* variables, which makes things behave a bit better.
What locale are you set to?