> your shell is broken. [0-9] are perfectly valid anywhere in a unix file > name.
does bash completion work for you on *anything*? Or does it get confused thinking that you are specifying a previous command (!### in the history)? Yes, a file/script named [0-9]* is valid, but still breaks things. Maybe there is some trick to get around it that I do not knwo about, but the big issues where those that the editor raised. EBo --
