ls bug

2002-04-27 Thread Andreas Feldmann
das programm ls hat nen bug: wenn man versucht ein verzeichnis auszulesen, das ein leerzeichen besitzt interpretiert er das leerzeichen des verzeichnisses als echtes leerzeichen: #> ls uni/malo/klausur\ zettel.pdf /bin/ls: uni/malo/klausur: Datei oder Verzeichnis nicht gefunden /bin/ls: zettel.p

Re: ls bug

2002-03-24 Thread Bob Proulx
> ls (fileutils) 4.1.5 does no more list > files with capital names first. This must > be a bug. It is the first time I see ls > behave like this. > (ls (GNU fileutils) 4.0p did it correctly) Thank you for your report. It is much appreciated. However you have hit a common RH problem and not an

ls bug

2002-03-24 Thread Oliver Knill
Hi ls (fileutils) 4.1.5 does no more list files with capital names first. This must be a bug. It is the first time I see ls behave like this. (ls (GNU fileutils) 4.0p did it correctly) Oliver Knill [knill@knill1:] touch A [knill@knill1:] touch

Re: ls bug

2002-03-09 Thread Matt Schalit
Edsel Adap wrote: > I would like to report what I think is a bug in ls. [snip] > Version info: > % ls --version > ls (GNU fileutils) 4.0l Thanks for taking the time to make a thorough post. May I suggest you download and try out the newest fileutils, 4.1.6, from your favorite GNU m

Re: ls bug

2002-03-09 Thread Bob Proulx
> I would like to report what I think is a bug in ls. > > Bug Synopsis: ls does not honor collating sequence of selected locale Thank you for your very detailed and well presented bug report. You did a great job with that. Since most of the bug reports we get are really terrible y

ls bug

2002-03-09 Thread Edsel Adap
I would like to report what I think is a bug in ls. Bug Synopsis: ls does not honor collating sequence of selected locale Description: ls always sorts its output using the C locale's collating sequence. That is all uppercase names are listed first before lowercase

Re: 'ls' bug ?

2002-02-21 Thread Bob Proulx
> The following "ls -lh" produces a 20megabyte report of the file size... [...] > Even though the file is 200 megabyte in size [...] > ls (GNU fileutils) 4.0x I cannot recreate your problem. 4.0x is getting old. Would it possible to see if the latest version 4.1, preferably the testing version

'ls' bug ?

2002-02-20 Thread Brian Schonecker
The following "ls -lh" produces a 20megabyte report of the file size... [bschone@endeavour bschone]$ ls -lh IRIX6.5.15m.tar.gz -rw-rw-r--1 bschone bschone 20M Feb 6 14:34 IRIX6.5.15m.tar.gz Even though the file is 200 megabyte in size [bschone@endeavour bschone]$ ls -l IRIX6.5.15m.

Re: ls bug report.

2001-08-08 Thread Albert Schueller
Quoting Albert Schueller ([EMAIL PROTECTED]): > > After a recent upgrade to Redhat 7.1 I'm noticing the following annoying > behaviour in ls. For many years now I've named directories starting > with capital letters so that in a standard file listing the directories come > first and then the res

ls bug report.

2001-08-08 Thread Albert Schueller
Hi, After a recent upgrade to Redhat 7.1 I'm noticing the following annoying behaviour in ls. For many years now I've named directories starting with capital letters so that in a standard file listing the directories come first and then the rest of the files. According to the ls man page this i

Re: ls bug?

2001-06-28 Thread Matt Schalit
Bob Proulx wrote: > > > I've just installed linux 2.4.4 and, much to my dismay, noticed the > > behaviour of ls has changed. Indeed, it would seem the leading dot in > > dotfiles is ignored when ls sorts its output. The result is a mess of > > regular files interspersed with dotfiles. I hope you

Re: ls bug?

2001-06-27 Thread Bob Proulx
> I've just installed linux 2.4.4 and, much to my dismay, noticed the > behaviour of ls has changed. Indeed, it would seem the leading dot in > dotfiles is ignored when ls sorts its output. The result is a mess of > regular files interspersed with dotfiles. I hope you realize how much of > an impa

ls bug?

2001-06-26 Thread Fady Habra
Hello, I've just installed linux 2.4.4 and, much to my dismay, noticed the behaviour of ls has changed. Indeed, it would seem the leading dot in dotfiles is ignored when ls sorts its output. The result is a mess of regular files interspersed with dotfiles. I hope you realize how much of an impact

Re: is this an ls bug?

2001-05-28 Thread Matt Schalit
[EMAIL PROTECTED] wrote: > > I'm not sure if this is raelly a bug, so apologies if this is mistaken. Not a bug, just a frequently asked question :) > ls -d only outputs ./ rather than a list of directories in ./ > > Is this the 'correct' behaviour? Yes it is. Sometimes you want to list w

is this an ls bug?

2001-05-28 Thread rednaxela
I'm not sure if this is raelly a bug, so apologies if this is mistaken. ls -d only outputs ./ rather than a list of directories in ./ Is this the 'correct' behaviour? Thanks for any help Alex ___ Bug-fileutils mailing list [EMAIL PROTECTED] http:/

ls bug?

2000-08-27 Thread Nick Marouf
Hi, I've run across this weird problem with ls. when I do an ls as so it shows the following. [marouf@server backup]$ ls -l total 27277472 drwx--3 root root 4096 Aug 21 21:02 home -rw---1 marouf admin120059167 Aug 22 16:06 server_2000-08-22.tar.save -rw-

ls bug

2000-07-22 Thread Yuri Kozlov
Hi, developer. I found a bug in `ls` command of fileutils-4.0w packet. This command make wrong sorting filenames with russian symbols. Patch included. WBR, Yuri Kozlov --- /test/fileutils-4.0w/src/ls.c Fri Jun 16 12:49:41 2000 +++ /test/fu/ls.c Sat Jul 22 17:24:33 2000 @@ -2146,13

'ls' ¿'bug' in Slackware 7? (fwd)

2000-07-05 Thread melendez
(CST) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: 'ls' ¿'bug' in Slackware 7? Hello, I'm using Slackware 7 at home and I found a abnormal behavior with 'ls' and latin1 characters. If I 'touch' a file with that characters then 'ls'

Re: Possible ls bug.

2000-05-25 Thread Bob Proulx
> [gpeters@cass gpeters]$ ls --version > ls (GNU fileutils) 4.0 > [gpeters@cass gpeters]$ ls -j > ls: invalid option -- j > Try `ls --help' for more information. > [gpeters@cass gpeters]$ ls -e > Try `ls --help' for more information. > > Is "-e" not an invalid option? Should it be reported as su

Possible ls bug.

2000-05-25 Thread Gavin Peters
[gpeters@cass gpeters]$ ls --version ls (GNU fileutils) 4.0 [gpeters@cass gpeters]$ ls -j ls: invalid option -- j Try `ls --help' for more information. [gpeters@cass gpeters]$ ls -e Try `ls --help' for more information. Is "-e" not an invalid option? Should it be reported as such? - Gavin --

ls bug

2000-04-14 Thread Kurt Glaesemann
When doing an ls in a directory with many files in a directory that is mounted over NFS, the ls command uses all availible memory on the machine. Copying such a directory with cp does the same thing. The directory has 3594 files in it. And the NFS server is not running Linux. Running the command

ls bug

2000-04-11 Thread Serge Wroclawski
This is a stupid bug, but it does exist... the -k option does not work with -l That's not mentioned in the man pages that I saw (RH and Debian GNU/Linux), nor the ls docs thatr I saw It's also in the --help, and nowhere does it mention it won't work with other options. I realize this is not so