text stringlengths 0 99.6k |
|---|
or too close to right or right > 80). |
NOTE: You can return to the menu at any time by pressing the STOP key. Also, |
pressing CTRL H (while in edit mode) will return a help screen to assist |
those who don't like to memorize control and function keys. |
The screen will clear and (if you used the default margin values) you will |
see bars at the left and right sides of your screen. These are the margin |
markers, and at the bottom of the screen will be a status line. You will not |
be able to type into the margin markers, as they are there to help you format |
your text and let you know where your lines start and end. All screen lines |
will be combined in pairs as 80 column lines, which will leave you with 12 |
lines on the screen at a time. You can identify which page, line and column |
the cursor is on by reading the status line at the bottom of the screen. The |
status line also tells you which mode you are in (40 or 80 column). Default |
mode is 80 column. 40 column mode can be invoked with CTRL X, for those who |
prefer to work with 40 column text (best for creating source code files or |
creating messages in 40 column format (non-standard text files). |
Type a line of text. At the end of the line, press RETURN to get to the next |
line, or just keep on typing. Words will not be broken at the right margin |
marker, because of the editor's automatic PARSING feature. If the last letter |
on a line is not a space, the editor will move the entire word to the next |
line for you. There are some safety features built into this routine, too. If |
there is text on the next line, parsing will not take place. This allows you |
to edit a previous line without accidentally dumping text on the next one. |
Also, parsing will not operate on words longer than 10 characters. That was |
done to allow the use of long strings of dashes for borders, etc. Parsing is |
there to allow you to type without having to watch the screen. Be wary of |
shifted spaces...the editor treats them as characters (not spaces), and they |
can cause unexpected results, especially if they are on the next line...the |
editor will not parse, thinking there is text there. This can be used to |
FORCE a word to stay on the previous line, should you want it to. |
CURSOR KEYS |
Cursor right and left work as you would expect them to. Cursor up and down |
are a bit different. They move the cursor 2 screen lines at a time (which is |
really ONE 80 column line). The insert and delete keys will work as expected, |
but only on the current line. When holding the delete key down, the cursor |
will make it's way only as far as the left margin. If you want to delete part |
of the previous line, move the cursor there with a cursor left, and then |
continue deleting. The insert key will push all text from the cursor position |
on towards the right margin. Text pushed into the right margin cannot be |
recovered. The home key works normally, but screen clear is not supported. |
SCROLLING THE SCREEN AND THE TEXT BUFFER |
Attempting to move the cursor past the bottom of the screen will cause the |
screen to scroll forward. Reverse scrolling will happen at the top of the |
screen. When you move the cursor to the end of available memory, forward |
movement will stop. The same is true for reverse movement at the screen's |
top. |
THE CTRL KEYS |
CTRL D will delete the current line and draw all forward lines in to close |
the gap. CTRL I will open up a blank line, pushing all lines forward from the |
current line on. Holding CTRL d or CTRL i will allow you to quickly delete or |
insert large portions of text. Even faster inserts and deletes are possible |
with the next set of keys (BLOCK CTRL KEYS). |
THE BLOCK CTRL KEYS |
These keys call routines which operate on a BLOCK of text (a block being one |
or more full lines of text). The first time a BLOCK CTRL key is pressed, the |
start of the block is defined and stored (it will be the line the cursor is |
on), and the cursor fast-flashes to let you know you have invoked a BLOCK |
function. The second time you press the BLOCK CTRL key, you should have |
already moved the cursor to the line you wish to designate as the last line |
in the block. That line will be defined as the end of the block, and the |
function will then be executed. |
NOTE: If you accidentally invoke a block function (the cursor will fast-flash |
when one is started), you can cancel it by pressing the STOP key. This will |
take you to the menu (where all editing functions are cancelled), and from |
there you can return to edit mode by pressing RETURN (selection 3 will be |
under the cursor). |
CTRL A (align a block) |
This command will "repack" a block of text between the margin markers. I |
frequently use it to convert 40-column text captured by my terminal's buffer |
to 80 columns for printing. Blank lines are preserved, but all extra spaces |
between words are eliminated (repacks with one space between words). If extra |
spaces between words are desired, use shifted spaces (they're treated like a |
character by the alignment routine). Here's an alignment demo: |
This is the first line. |
This is the second line. |
This is the third line. |
Now here are the same 3 lines repacked with CTRL A: |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.