Differences

This shows you the differences between two versions of the page.

--- tutorials:exec [2022/03/14 04:24]
papa [Command and argument list]
+++ tutorials:exec [2022/03/15 09:41] (current)
papa [Automatic commands]
@@ Line 26: / Line 26: @@
   * In the middle of command name input, pressing ''?'' lists TOPS-20 commands beginning with the characters entered so far.
   * Elsewhere, pressing ''?'' lists or describes possible arguments at the current position.
+===== Completion and guidewords =====
+During command entry, pressing **Esc** will complete partial commands and arguments and display //guidewords//.
+//Guidewords// (also called "noise words") are parenthesized words or phrases that EXEC inserts into the command text to describe the command or the arguments expected. Guidewords are only for documentation and are ignored during command processing. For example, entering "di**Esc**" at the EXEC prompt will cause EXEC to insert the following characters into the command text:
+  @diRECTORY (OF FILES)
+... and wait for the user to specify what files he wants listed, or press **Enter** to list all files in the current directory.
 ===== Abbreviations =====
@@ Line 41: / Line 51: @@
 | LOGOUT | LOGO |
+===== Command line editing =====
+Use the following control keys to edit command text before pressing **Enter** (except for **Ctrl-H**).
+| **Backspace** | Delete last-typed character to the left. |
+| **Ctrl-R** | Retype current command line. |
+| **Ctrl-U** | Erase current command line. |
+| **Ctrl-W** | Erase previous word. |
+| **Ctrl-H** | Reprint erroneous command up to error.<sup>*</sup> |
+<sup>*</sup> When EXEC detects an error in an entered command, it will display a "?" and possibly an error message.  Pressing **Ctrl-H** will retype at the EXEC prompt the command text up to the location where EXEC detected the error, allowing the user to correct just the erroneous portion and reenter.
 ===== Subcommands =====
+To enter subcommands, type a comma ('','') at the end of the command line before pressing **Enter**. EXEC will respond with the subcommand prompt (default ''@@''). Enter a subcommand and press **Enter**, repeating for as many subcommands as you wish to specify. Press **Enter** on a blank line to end subcommand input and EXEC will process the command with the specified subcommands.
-[Put general information on using EXEC here. (Completion, guide words, command line editing, help ...)]
 ====== Command Files ======
@@ Line 76: / Line 92: @@
 | SUBMIT | 1. SYSTEM:BATCH.CMD \\ 2. BATCH.CMD \\ 3. SYSTEM:COMAND.CMD \\ 4. COMAND.CMD |
 | PUSH | 1. SYSTEM:COMAND.CMD \\ 2. COMAND.CMD |
+| ATTACH | 1. ATTACH.CMD |
 | LOGOUT | 1. LOGOUT.CMD \\ 2. SYSTEM:LOGOUT.CMD |
 When EXEC executes multiple command files, commands in earlier command files may be overridden by commands in later files. For example, during log-in a ''SET PROMPTS'' command in a user's LOGIN.CMD may be overridden in SYSTEM:COMAND.CMD since it is executed later in the sequence. This may be the case if EXEC seems to be ignoring commands in your LOGIN.CMD. Try moving such commands to your COMAND.CMD file, which is executed last in the log-in sequence and will override any conflicting commands in SYSTEM:COMAND.CMD.
+In principle, your LOGIN.CMD file should contain programs you want to run automatically when you log-in and job-wide customizations (DEFINE, SET LOCATION), while your COMAND.CMD should contain local EXEC customizations that you want applied every time EXEC starts for both LOGIN and PUSH (SET DEFAULT, SET PROGRAM, SET PROMPT
+or PCL declarations).

TOPS-20 User Wiki

User Tools

Site Tools

Differences

Page Tools