T.R | Title | User | Personal Name | Date | Lines |
---|
1876.1 | That raises a question. | RAVEN1::EVERHART | | Mon Nov 14 1988 09:50 | 5 |
| Does this only work with ARP? Or does it only work without
ARP?
- Chris
|
1876.2 | Should work without ARP... | 32341::RAVAN | | Mon Nov 14 1988 16:13 | 3 |
| That is a pure AmigaDos command. It should work without ARP.
-jim
|
1876.3 | | RAVEN1::EVERHART | | Fri Nov 18 1988 13:30 | 7 |
| I'd like to add that this sort of works like a typewriter, but it
has the added advantage of letting you correct your mistakes BEFORE
entering the line. But, I think I'll stick with word processors.
:-)
- Chris
|
1876.4 | | TLE::RMEYERS | Randy Meyers | Fri Nov 18 1988 17:41 | 6 |
| By the way, to make your Amiga stop acting like a typewriter, press
control-\.
I think that ARP may break this command. In a fit on incompatibility, ARP
made * mean a pattern matching all files instead of meaning open the current
window as a file.
|
1876.5 | copy >prt: for arp | MIST::TBAKER | Tom Baker - DECwest CSSE | Fri Nov 18 1988 17:48 | 5 |
| With ARP COPY >prt: works like a typewriter. I'm not sure if
control \ stops the typewriter. I'll have to try that. I used
control z to stop. I think I'll stick to my editor and then print.
tom
|
1876.6 | Humor | TLE::RMEYERS | Randy Meyers | Fri Nov 18 1988 17:52 | 24 |
| Re: .0
On a related topic:
Are you every to busy to write a small program to do something? Entering
the editor, typing the source, compiling and loading it is just too slow?
Just type * as the name of the command at the CLI prompt. As in:
1> *
The CLI will wait for you to type in a executable file in binary. You can
use the alt shifts to type in those bytes with values greater than 127,
or you can load your own custom keymap to make the job easier.
It takes a little while to learn the "hunk" format of an Amiga executable
file, but once you do, you'll find that your programming productivity
really speeds up! I haven't touched the C compiler in weeks!
If you decide not to type in a executable, typing about 4 control-\'s will
cause the CLI to give up.
I don't know if this works using the 1.3 Shell. The Shell checks the
execute-allowed protection bit before loading a program.
|