There are 13 other files named sed.bwr in the archive. Click here to see a list.
BEWARE FILE FOR THE SED SCREEN EDITOR
To report bugs and deficiencies, to ask questions or make
A CHRISTOPHER HALL
Software Engineering - MR1-2/L10
Digital Equipment Corporation
200 Forest Street
The SED editor is a new program. it has been tested in all the ways
I can think of, and used by a limited but sophisticated group of people
(most of the editor, and all its documentation, was written using SED).
Its reliability should be pretty high, but undoubtedly some features have
not gotten as much exercise as others. So there are probably a couple of
arcane bugs lying around. If you find any please report them, with as much
helpful information as possible.
(SKIP THE FOLLOWING PARAGRAPH IF SED IS NEW TO YOU)
If you have a version of SED earlier than edit level 101 be advised
that the internal command values have changed. The effect is to rearrange
the keyboard layout, changing only the commands invoked by ^K, ^L, ^N,
^U, AND ^V. If you do not want to make these changes, clear the assembly
parameter "NEWTAB" (ie make it NEWTAB==0) in SED.MAC. The documentation
reflects the new table, so if you want the old arrangement regenerate
the documentation with the "oldtab" variable set. like:
Do the same for SED.RND and SED.RNO.
SED runs on any processor that runs TOPS-10 or TOPS-20. However, if
you have a KA-10 set the assembly parameter "FTKA10" in SED.MAC (FTKA10==1).
SED currently reads the file to be edited into core and
writes it out on exit. This limits the size of the edit file, the exact
restriction depending on the system's memory and virtual memory.
It is planned to upgrade SED so that it pages the file in and
out on its own, so it will be able to handle files of any size, but
itself be very small.
If you define both the current file and the alternate file to be the
same file, when you do set-files to toggle back and forth the first line
on the screen may not be complete. Currently nothing is done to update the
pointer to the start of the screen for the alternate file, so if text is
inserted or deleted that pointer will not be correct (no harm is done if
the current file is not changed).
If your terminals run at 9600 baud you may have a problem with the terminal
sending XON-XOFF pairs when it feels overworked. SED has a hard time
telling those characters from the ^S and ^Q commands. The easiest solution is
to avoid using ^S and ^Q as commands and set the npg flag to tell SED
to keep tty page in effect (read SED.MEM, the installation guide, if you
don't understand this). See the keyboard layout in SED2.KYS for a suggested
arrangement of keys which does not use ^S and ^Q.