orking anymore
On 04 October 2006 18:08, Andy Telford wrote:
> Nope. The directory was not empty, so * should have been expanded by the
> shell according to the bash "pathname expansion" rules. I included the
> SHELLOPTS variable in the first email to show that noglob is not
Nope. The directory was not empty, so * should have been expanded by the shell
according to the bash "pathname expansion" rules. I included the SHELLOPTS
variable in the first email to show that noglob is not set.
$ mkdir newdir
$ cd newdir
$ touch newfile
$ ls
newfile
$ ls *
ls: *: No such fil
Has any experienced this?
- "ls" works but "ls *" returns "ls: *: No such file or directory"
- same if I just use the shell builtin "echo *" just returns "*"
I am up to date with the latest versions of everything. I had to fix up the
line endings in my .bash_profile/.bashrc file to follow the
3 matches
Mail list logo
