home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Club Amiga de Montreal - CAM
/
CAM_CD_1.iso
/
files
/
007.lha
/
cle.doc
< prev
next >
Wrap
Text File
|
1986-11-10
|
3KB
|
69 lines
CLE: Command Line Editor
CLE meets two needs in a Command Line Interpreter (CLI) environment:
1. Editing within the current command line,
2. Recall (and possibly editing) of previous command lines.
The "arrow" (cursor movement) keys control movement both within the current
and previous command lines. "Left" and "Right" arrow are used within the
current line to move the cursor. "Up and "Down" arrow are used to roll back-
and for-word through previous command lines (but will only work if the cursor
is at the end of the command line).
The only way to correct mistakes under CLI is either to backspace through the
mistake, then re-enter everything you just backspaced over, or rub-out (Ctrl-X)
the entire line and start over. Being able to move the cursor makes it much
easier to correct typing mistakes. Just position to the typing error with the
"Left" or "Right" arrow keys and backspace over the mistake. Note that back-
space removes characters to the left of the cursor. If the mistake is under
the cursor, the "DEL" key will remove it. To insert new characters, just start
typing. CLE is always in "insert" (as opposed to "over-strike") mode.
In addition to command recall and extended command line editing, CLE has
a slightly different approach to finding commands than the CLI search "PATH".
The directory search sequence for CLE is:
1. Current directory,
2. RAM:C,
3. C:,
4. sys:system,
5. S: (It will Execute a command file in the S: directory without you
typing: Execute 'command_file_name'. Just type the command file name).
If you need to get out of CLE, or start a new copy, the commands are:
exit -- ENDCLI (same as under CLI),
start -- CLE (As you do to start CLE in the first place).
Constraints
-----------
1. CLE currently saves the last 23 command lines.
2. Some messages (such as from programs that execute the "RUN" command) go
to the CLI window where CLE was started (Even if other copies of CLE have
since been started). If you need to see them, use the "Window-to-Back"
(black square over white) gadget at the top right corner of the screen. In
some cases, the reverse happens. The output from a command will go to the
CLI window, but the message from RUN will go to the CLE window (under CLE,
try: "RUN cd").
3. The Amiga DOS library function "Execute" seems to access "C:" to use the
"RUN" command. If it is assigned to a disk directory, CLE will access that
disk for every command line (even it it finds the command you want in RAM:).
Hopefully, Commodore will upgrade the Execute function to use the search
path for accessing "RUN". EMACS seems to suffer a slightly stranger addic-
tion to disk. It requests the CLI disk if it has been removed, but proceeds
if you "Cancel" it's requestor. Beware of only copying some commands into
RAM:C, then assigning C: to it. If a program needs one of the commands you
didn't copy, it will fail. In that case, REMEMBER: the error message may
have gone to the CLI window (see constraint 2).
----------------- End of CLE.DOC ----------------- 11/02/86, S.D. Maley