|
|
1.1 ! root 1: Copyright (c) Stichting Mathematisch Centrum, Amsterdam, 1984. ! 2: ! 3: HOW'TO TRY the B editor: ! 4: ! 5: The directory B/ex/try is here to try the B editor interactively. The ! 6: example B workspace here can always be regenerated with: ! 7: ! 8: cd ../generate ! 9: cp \'* ../try ! 10: cd ../try ! 11: ! 12: Now enter the B system from this directory with ! 13: ! 14: ../../bin/b ! 15: ! 16: After the B system has started up it will prompt for a command with ! 17: ! 18: >>> ? ! 19: ! 20: Slowly type `s', then `t', (no capitals needed) and you should see the B ! 21: editor suggest the SELECT and START commands, respectively. Now ! 22: press [TAB] to accept this last suggestion, and [RETURN] to enter the ! 23: START command to the B interpreter. This command will promt you for ! 24: input, with ! 25: ! 26: ? ! 27: ! 28: Just enter about four lines of text, (which will be echoed), ending with an ! 29: empty one (press [RETURN] immediately). A short `poem' should be generated ! 30: by the B interpreter. ! 31: ! 32: If you are already familiar with the B language, you might try to edit the ! 33: START unit by answering ! 34: ! 35: >>> ? ! 36: ! 37: with ! 38: ! 39: :START ! 40: ! 41: For example, try to remove the SET'RANDOM command, to get random ! 42: results on the same input. Or make the unit delay the echoing of the text, ! 43: entered by the user, until after the reading of the empty line. For test- ! 44: ing purposes you should at least try the arrow keys to move the focus ! 45: around. ! 46: ! 47: You can undo any change by pressing [BACKSPACE]. ! 48: You can get help with ?. ! 49: You can leave the B editor with control-X. ! 50: You can leave `b' by typing QUIT. ! 51: ! 52: For more information, see the manual pages `B(1)' and `bterminal(5)', and ! 53: the User's Guide. ! 54: ! 55: See the B Newsletter, issue 2, for a description of the `generate' program. ! 56: ! 57: If there are any problems with the editor, consult the `bterminal(5)' ! 58: manual entry before trying anything else.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.