Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!CHPC.BRC.UTEXAS.EDU!ezab066 From: ezab066@CHPC.BRC.UTEXAS.EDU.UUCP Newsgroups: mod.computers.vax Subject: CD to a Subdir Before Creating It Message-ID: <8702202237.AA23028@ucbvax.Berkeley.EDU> Date: Fri, 20-Feb-87 12:28:00 EST Article-I.D.: ucbvax.8702202237.AA23028 Posted: Fri Feb 20 12:28:00 1987 Date-Received: Sat, 21-Feb-87 10:14:12 EST Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: "Albert Wu ( CEM-UT )" Organization: The ARPA Internet Lines: 31 Approved: info-vax@sri-kl.arpa >> Someone recently said it was 'sad' that SET DEFAULT does not >> complain when you set to a non-existent directory. >> >> I hope they don't "fix" this. My common method of creating a >> new directory (since I'm almost always going to work in it very >> next thing) is: >> >> $ SET DEFAULT [.ONE.TWO.THREE] >> $ CREATE/DIR [] >> ... >> Checking whether a directory you're setting to exists is easily >> done in a command procedure... Setting default first to a nonexistent directory and then create the directory tree is illogical to me. In the first place, how do you know that you want to create such a new directory tree without knowing what directories you already have existing. The new subdirectories that you're creating might possibly be something similar to what you already have. You don't want to confuse yourself by creating a lot of vaguely different sub-directories, do you ? It's more logical to first look at a directory tree. Then, decide if the new file fits in any of the existing sub-...-directories. If it does not, then you create the new sub-...-directory. To show the directory tree with a command procedure, one must be able to identify all the directory files, and one must be able to check whether a file with type DIR is a real directory file, all within a command procedure. ------------------------------------- Albert Wu ARPANET: EZAB066@CHPC.BRC.UTEXAS.EDU BITNET: EZAB066@UTCHPC.BITNET ------