re: suspected 'ls' recursive listing when NOT requested bug in V6.4 GNU CoreUtils

[andrew scott]

Dear GNU people,

Re: Core Utils V6.4 'ls' command

I am in my home directory.  I make a new sub-directory
called 'p001_project'.  I have a file at the home
level called 'p001_data.c'.  I use an ls command like
this:-

ls -ls p001*

and I get the file listed as expected.  I then move
the file from home into the sub-directory and repeat
the ls command:-

ls -ls p001*

and, amazingly, the file is still listed.  Note that I
have NOT used the -R switch to ls, which would then
make the command recursive.

If instead, I use this command:-

ls -ls p001_data.c

I get NO files listed.  If I then issue this command:-

ls -lsR p001*

then I get a heading from ls saying there is a
sub-directory present, in which the file is then
listed as expected.

It seems to me me that somehow, if there is a wildcard
present (the '*' in this example) then the command
goes recursive on sub-directories without printing out
the sub-directory heading.

This problem has caused me considerable pain and lost
time, because I originally thought that somehow a hard
link had been set up in my filesystem.  Trying to
remove that link proved impossible and has resulted in
my thinking changing to that reported above.

If you can figure this out I'd appreciate a reply in
the form of an email, but please do not send me either
a binary or new source because my machine is not set
up to receive email (I am using a public facility to
send this!).

With best regards,
Andrew Scott, Cambridge, UK.



        
        
                
___________________________________________________________ 
New Yahoo! Mail is the ultimate force in competitive emailing. Find out more at 
the Yahoo! Mail Championships. Plus: play games and win prizes. 
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk