On Tue, 23 Sep 2003, [ISO-8859-1] Christian Ridderström wrote: > This behaviour is actually identical to *nix shells, you have to quote the > argument... for instance by doing: > dir "\program files" > > The reason that you get two "File Not Found" is because you're trying to > list '\program' and '.\files'...
Yes, I KNOW you can do that. My point is that you shouldn't have to :-) > I've never heard of such a rule, and quite often use spaces (and åäö) in > my names... Guess we must have learned *nix from different sources, then. IIRC - it has been a couple of decades - not using characters such as <, >, &, or space was one of the basic "Intro to Unix" things. Though as you learn more (or make more mistakes), you learn that if you try really hard, you actually can put most or all of them in names. You can, I think, even put quotes in names, and make your life really interesting :-) But why do you want to make things difficult? Putting odd characters in names will, as we've seen here, break some programs. Don't know about you, but I have much better things to do with my time than figuring out that my Lyx document doesn't print because I included a file with a non-standard character in it. If I stick to alphanumeric chars, I can confidently elminate that class of error :-) James
