text stringlengths 0 1.99k |
|---|
k-rad commands! |
Conclusion: |
I hope you have enjoyed this file. Watch for updated versions in Phrack. |
If you have problems finding Centagrams, here are a few nets: 214-733-XXXX, |
415-647-XXXX, 408-790-XXXX. I can be reached at 214-733-5294. Don't play with |
my net. If I see idle mailboxes getting taken over I will just get rid of |
them. There are plenty of other networks. Special thanks to: Taran King Knight |
Lightning, SJE, The Egyptian Lover, and Ryche. Some added notes: Call the |
Attila the Hun/Master Blaster loser line at 214-733-5283. |
(C) Quest/Sentry Productions 10/13/86 |
==Phrack Inc.== |
Volume One, Issue Nine, Phile #4 of 10 |
$$$$$$$$$$$$$$$$$$$$$$$$ |
$ PROGRAMMING RSTS/E $ |
$ File2: Editors $ |
$ by: $ |
$ Solid State $ |
$$$$$$$$$$$$$$$$$$$$$$$$ |
Written (c) Oct 11, 1986 |
------------------------ |
Within this article I will be focusing on the TECO text editor found on |
almost every installation of RSTS that you will pass by today. I feel it is |
unneeded to do a write up on the other editors such as EDT, a screen editor |
for VT100 and VT52 terminals, and EDFOR, a FORTRAN text editor, as most |
hackers will not have the proper hardware/software at their disposal. |
This file does not contain many tricks, but has straightforward information |
that most assuredly can be found in the user manual. Since not everyone has |
access to help documents though, this file will provide a base for the first |
time editor user and hopefully a reference for the experienced. If you feel |
otherwise.. don't waste your time reading it. |
Following the main portion of the file is an updated copy of the decoy |
trick I promised to revise that was featured in my first file. Hopefully, (I |
am not promising though), I have succeeded in removing all the bugs this time. |
USES |
==== |
A text editor, for those of you that happen to be brain dead, is a utility |
similar to the word processor you use everyday on your micro: it allows a |
person to create, modify, and compile text files. But, also can edit, and if |
need be, create program files. For these reasons and many others, knowing how |
to use an editor thoroughly can be a major advantage to the hacker on future |
explorations. |
EXECUTING |
========= |
Typing TECO invokes the TECO text editor. If TECO is just typed without any |
modifiers, then the file edited last will be placed in the editing buffer. |
(More on this subject can be found below under MEMORY.) To edit a different |
file, or create a new file, the following forms are used: |
TECO filename.ext To edit an existing file. |
TECO outfile.ext=infile.ext To edit from one file to another. |
MAKE filename.ext To create a new file. |
Other ways to execute TECO involve VT terminals, but we are not going into |
that much detail within this text. |
INITIALIZATION |
============== |
If there is a file named TECO.INI in your directory when TECO is invoked, |
it is assumed to be the macro settings for a VT terminal. We don't need to |
bother with those, so make sure to disable the search by appending the switch |
/NOINI on execution. |
MEMORY |
====== |
Each time TECO is executed, the name of the file being edited is placed |
into another file titled TECFnn.TMP where nn is your job number. If you invoke |
TECO and wish to edit a file different than the one currently in the memory |
file, select the switch /NOMEMORY. |
MODIFIERS |
========= |
There are a number of options, called switches, which modify the execution |
of the TECO utility. Some like /NOINI and /NOMEMORY I have previously |
mentioned. Other important switches follow along with a short description of |
each. To select one of these options, append it to the call string when you |
invoke TECO: |
TECO filename.ext /[option1] /[option2] ... |
/FIND This places the pointer at |
the last marked position |
within the input file. |
/INSPECT If selected, you can only |
read the file, not edit. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.