CompuServe Thread

Special Charecters

1 messages in this thread
#18229From: Doug WingerOct 23, 1988 11:57 AM
Ross, Try a DIR with wildcards. LIST requires the PAT(tern) switch to use wildcards. (eg) list telecom.1: pat lowel#? It is NOT a good idea to allow spaces in filenames, as you've just found out, and may introduce those really nasty times when you 'add' spaces to the front or tail of the filename. I had a file named 'stuff to do' and accidently added to spaces to the end, so it would only respond directly to a "Stuff to do " SOP 'round here is to use the '_' underscore as a space equivalent, so you'd have lowlell_tech as a filename. Once you get a handle on the file, RENAME it to something easier to 'grab', and avoid spaces except on aethetic grounds. 8) Oh, before I forget…if you are using WB, and the file has an associated icon, then all these arguments I've made don't hold. Using the WB rename obliviates the need to worry about that, as it uses a requester you can clear before renaming, and guarantees it will respond to whatever name you've given it. Doug