Re: Weird problem with function ls or system("ls...")

[Christian Weickhmann]

My ls gives me: ls (GNU coreutils) 6.10

> does. Because apparently, you have no file that matches * in the working
> directory (. and .. can't be globbed). So the shell just forwards the
> star as an argument. Then ls complains because it can't find a file
> called *.

Look at the different behaviour:

The directory is empty.
But for ls * it gives me an empty set but return code 0 (all fine).
For ls *a* it gives me an error (return code 2).

If both would return an error, I'd say; yes it's consistent. :)
This way I wonder why it is.

John stated that octave uses the system's ls command, so I will look at the 
mailinglists there.

Thanks so far. (Still weird though... ;) Today I thought my computer just 
mocks me...).

Good night,
Christian