Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!cbmvax!vu-vlsi!swatsun!schwartz From: schwartz@swatsun.UUCP Newsgroups: comp.unix.questions Subject: Re: dsb unix vs. dec's vms Message-ID: <1135@byzantium.swatsun.UUCP> Date: Tue, 19-May-87 10:36:16 EDT Article-I.D.: byzantiu.1135 Posted: Tue May 19 10:36:16 1987 Date-Received: Thu, 21-May-87 00:57:16 EDT References: <5828@shemp.UCLA.EDU> <34ab0e42.8be4@apollo.uucp> <667@bsu-cs.UUCP> Organization: Swarthmore College, Swarthmore PA Lines: 24 Summary: vms remembers past command lines. In article <667@bsu-cs.UUCP>, dhesi@bsu-cs.UUCP (Rahul Dhesi) writes: > But since the command > interpreter effectively does an exec() each time it executed a user > command, it can't save information and reuse it very easily--the > next command is really executed by a brand-new invocation of the > command interpreter. Disclaimer: I don't use VMS very often and I don't like it much. But: I do know that if you hit the key the shell gives you the previous command line. Repeat n-times and you get the nth previous command line. If it can do this, I can't believe it couldn't support multiple commands on one line. Speaking of fun command interpreters, Primos supports a command language that penalizes you for hitting too many times (the exact number of times is set by your system administrator, I think). Also, you can construct an infinite recursive loop in the command processor that eventually terminates with "FATAL$ USER ENVIRONMENT REINITIALIZED" -- # Scott Schwartz # UUCP: ...{{seismo,ihnp4}!bpa, cbmvax!vu-vlsi, sun!liberty}!swatsun!schwartz # AT&T: (215)-328-8610 /* lab phone */