| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 317.1 | Time for a shell | NOVA::RAVAN | | Wed Feb 11 1987 20:16 | 3 |
| nope. I strongly suggest getting a shell.
-jim
|
| 317.2 | | ECC::JAERVINEN | impersonal name | Fri Feb 13 1987 04:38 | 2 |
| What shell?? There seem to be so many floating around.
|
| 317.3 | Drew/Dillon shell | NOVA::RAVAN | | Fri Feb 13 1987 11:06 | 5 |
| True, there are many floating around. I'm using Steve Drew's version
(2.40M?, I think) of Matt Dillon's shell. I think it is very nice.
A network source for this shell is mentioned elsewhere in this notes file.
-jim
|
| 317.4 | | TLE::ANDERSON | Mike Anderson | Fri Feb 13 1987 18:24 | 12 |
| re:.3
The Drew/Dillon shell is the best I know of -- especially if you
value the DCL style of command recall and editing. You also get
to avoid the sound of your disk drive every time you do a CLI command,
since most of the commonly used commands are built into the shell.
It also has aliasing, variables, redirection, search paths, flow
control in command files, control of return status values, and lots
of other features (most of which I haven't used yet). And the price
is definitely right.
Mike
|
| 317.5 | | ECC::JAERVINEN | impersonal name | Mon Feb 16 1987 03:37 | 15 |
| In the meantime, I got a copy of the Drew/Dillon shell - really
great. I have a CLI-only disk that loads the shell at initialization
(and a couple of external commands to RAM:), and I can the remove
the boot disk and still issue most commands without putting it back.
I had one problem though (I'm probably doing something wrong):
I ask for current date/time in startup, and then try to check
_maxerr to ask again if the format wasn't correct. First, I clear
_maxxerr, then ask for time, then I have a line roughly like
if $_maxerr>0; goto again; endif
but this seems to branch to the label 'again' every time...
|
| 317.6 | Shell Script Files | CGFSV1::DREW | Steve Drew | Mon Feb 16 1987 18:38 | 34 |
|
A couple of things (from memory).
> if $_maxerr>0; goto again;endif
You do need spaces here eg, if $_maxerr > 0;goto again;endif
^ ^
Also you could also use the _lasterr symbol since it will contain
the value of the last executed command. _maxerr only gets set with
the highest error to date.
Another method of error trapping in script files (my favorite)
is the except handler.
eg.
#Get date check if valid
# show current date, allow just a CR to keep that date
label again
set _except "1;echo Please Re-enter; goto again"
date | input d; echo -n Enter Date [$d] ;input newdate; DATE $newdate
unset _except d newdate
the Shell script files are actually very powerfull, just take a
little getting use to.
Hope this helps.. /Steve.
|
| 317.7 | | ECC::JAERVINEN | impersonal name | Tue Feb 17 1987 08:54 | 3 |
| I'll give it a try... I think I got a "redirection error" with
spaces around the > though...
|