Path: utzoo!utgpu!watmath!clyde!att!ucbvax!ELYSIUM.BERKELEY.EDU!dillon From: dillon@ELYSIUM.BERKELEY.EDU (Matt Dillon) Newsgroups: comp.sys.amiga Subject: Re: Multiple commands on a CLI line Message-ID: <8812011846.AA04769@elysium.berkeley.edu> Date: 1 Dec 88 18:46:52 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 66 :Hmm.... I started using Matt's shell (version 2.10 I think, the one :recently posted to comp.sources.matt-dillon) *after* I got 1.3 running. I :use the shell along with REZ, although given the preponderance of built-in :commands in the shell I don't have to REZ very many things. : :I thought about using the 1.3 Shell, but Matt's shell gives me a couple of :ultra-key features, like * wildcards, fast built-in commands (including a :'mv' command which does exactly what I *want* it to do) and local shell :variables to go along with the global 1.3 environmental variables (Matt: any :reason you've got SETENV but not GETENV? INCENV and DECENV might also be :useful), a combination I've been able to make good use of (My shells keep :track of they're own garbage using local variables, and communicate with :other shells via the ENV: variables). Plus, it can talk IPC, which I'll make :use of as soon as I get Dmouse 1.11. No need for a GETENV() call, since enviroment variables are in the $variable domain. i.e., echo $EnviroVarName. This is the 'GetEnv'. The way $varname works is that it first searches the internal (local) variables, then the enviroment variables. The local var search is case sensitive while the enviroment variable search is not. (1) $var local? (2) $var in enviroment? Also, note that alias's are also searched for in ENV: ... the command searching works like this: (1) local alias? (2) Enviroment variable-alias? (3) Internal command? (4) External command? :So: is there any really good reason to use the AmigaDOS shell instead of :Matt's? Well, the AmigaDOS shell can be made resident while mine cannot. There are probably some other minor compatibility problems (like the one people found with SPEAK:) but apart from that there is no reason. Well .. Execute Scripts and most script related BCPL commands are not supported by my shell, but for those you can just RUN them or spawn a CLI to handle it. Also, please make a distinction between my shell and Steve Drew's spinoff. The only *big* difference is that Steve added console line editing while I didn't (I just use ConMan). :Thanks for the great software, Matt! Welcome! :..- -- .. --. .- .-. ..- .-.. . ... .- -- .. --. .- .-. ..- .-.. . ... :| Neil Weinstock | att!cord!nsw | This mind intentionally | :| AT&T Bell Labs | nsw@cord.att.com | left blank | :..- -- .. --. .- .-. ..- .-.. . ... .- -- .. --. .- .-. ..- .-.. . ... : . o . o . // O -Matt\|/ * Oh Foo, missed again.