where D is the device number of your disk drive. Download it in .prg format.

When first run, svicc automatically unpacks a built-in tutorial on the basic use of svicc, and by extension, vi. Beginners should read through the built-in tutorial using the CRSR keys to scroll, as it explains basic ideas about how the editors both operate. The remainder of this page, however, is intended for those who are already familiar with vi. Please read svicc's built-in documentation beforehand if you are not proficient in vi.

svicc was originally based on Chris Miller's "Mr. Ed" screen editor package, as published in Transactor September 1987. While some of the original code is still present in some form, I (Cameron Kaiser) have since done significant optimization and cleanup, as well as adding in vi/ex commands, filesystem operations, editor improvements, primitive cut-and-paste, and vi-style editing behaviour.

With regard to editing, svicc is a scrolling editor, and every physical screen row corresponds to exactly one logical screen row. You must scroll using the motion keys to view lines longer than the screen is wide. svicc enforces a maximum line length of 249 characters. There is only one 255-byte yank buffer, which may hold up to one complete line of text, from the most recent delete operation (either x, X, or dd). The document buffer is 38,652 bytes (the size of the entire BASIC text space, minus 259 bytes for the BASIC execution stub and housekeeping).

svicc remaps certain keys for convenience. The CRSR keys are synonymous with the h j k l motion keys. RUN/STOP doubles as both ^C (interrupt) and escape key, acting as interrupt when entering an ex command, and escape at all other times. Use F7 for a true escape key.

On the Commodore 128 in 64 mode, the C128's ESC key is mapped to escape for insert and command mode only. (Yes, you can read the 128's special keys in 64 mode.)

Other than those conditions noted above, these single keystroke commands function identically in svicc:

These double keystroke commands function identically in svicc:

They are the only valid multi-key sequences. No other methods of specifying a count or a motion sequence are accepted. If you enter non-zero digits other than 1, they are treated as 1, and the count can never be greater than 1 (effectively thus only salient for G).

^ (caret, or up-arrow) is considered synonymous with 0, and svicc will warn you about the behaviour difference.

During complex or slow operations, a spinning "busy" cursor may appear in the bottom right corner to soothe your anxieties.

When in insert mode, you can insert characters other than standard alphanumerics and punctuation, and even some control characters. This shall be considered a feature, but do note that control and graphic characters will incorrectly appear as ordinary text on screen (though they will be saved in their true form), and inserting certain control characters may make your document difficult to edit.

As stated previously, svicc comes with a default document. To start with a clean document buffer, use :new and svicc will reset to an empty file.

To specify and load a file to edit, use :e filename to load a file from the default device (the most recently accessed disk drive). If the load fails, the document buffer will be rendered blank. The error channel is reported at the end of the load.

:q quits svicc and returns you to BASIC, but an important difference from standard vi is that providing you do not change BASIC text, enter program lines, etc., your document can usually be resumed fully intact if you return to svicc. svicc will tell you how to return, usually by entering RUN (again, assuming no changes made to the BASIC text area). Think of this as the Commodore version of a "shell escape."

If the current document buffer has been modified, all of the previous commands will refuse to function unless they are followed with ! (e.g., :new! must be used).

As in regular vi, to write a file to disk, use :w filename and the document buffer will be saved to the default device. Keep in mind that you must specify a filename, even if you are already editing a file (considered a feature thanks to DOS error #63). The error channel is reported at the end of the write.

A primitive DOS wedge is included in svicc using :@command (if command is blank, the error channel is displayed). The wedge operates on the default device. If $ is used as the command (e.g., :@$), the disk directory is displayed (press any key to return to editing); otherwise, the command is sent and the drive response displayed.

You may not group commands (e.g., :wq! is not allowed).

Fans of Rumiko Takahashi should look for the Easter egg.

The larger a document is and the closer you are to the top of it, the more work svicc has to do to insert characters (since it has to move almost the entire document for each character you type as you get closer to the beginning of the document).

Thus, editing within svicc is at its fastest at or near the end of a document, and faster still if the document is smaller.

You can also scroll up and down through documents slightly faster if you put the cursor at the beginning of lines (use the 0 command).

1. Enter or load your document into the document buffer.
2. Exit to BASIC with :q and then save it to disk using SAVE"FILE",D where D is your disk drive. This will save your document, along with a short BASIC stub, to a regular executable PRG file.
3. Using a machine language monitor, save the area from $c000 to $ced7, where svicc's main logic occupies.
4. Use your linker to link the ML portion with your saved stub-and-document file to create the final executable.

As this constitutes a derivative work, you must credit svicc in your document -- see the license.

• Faster, faster, faster!
• It would be nice if at least graphic characters were displayed properly, although the logic is a bit expensive.
• G is not implemented very efficiently, mostly for reasons of code size.

Original works and editor code, copyright 1987, Chris Miller. All rights reserved. Use of original "Mr. Ed" source code in accordance with the Transactor licensing policy.

svicc vi enhancements package and optimization/bug fixes, copyright 2003, Cameron Kaiser. All rights reserved.

I, Cameron Kaiser, am the author of the current release package and its primary maintainer, and all bug reports should go to me at ckaiser@floodgap.com.

Your use of this program indicates your binding acceptance of all license terms.