POSIX revision 1.1
1This version of ed is not strictly POSIX compliant, as described in the
2POSIX 1003.2 Draft 11.2 document.  BSD commands have been implemented
3wherever they do not conflict with the POSIX standard.  For backwards
4compatibility, the POSIX rule that says a range of addresses cannot be
5used where only a single address is expected has been relaxed.
6
7The BSD commands included are:
8	1) the `s' command (i.e., s[rgp]*) to repeat a previous substitution,
9	2) the `W' command for appending text to an existing file,
10	3) the `wq' command for exiting after a write, and
11	4) the `z' command for scrolling through the buffer.
12BSD line addressing syntax (i.e., `^' and `%').  is also recognized.
13
14The POSIX interactive global commands `G' and `V' are extended to support
15multiple commands, including `a', `i' and `c'.  The command format is the
16same as for the global commands `g' and `v', i.e., one command per line
17with each line, except for the last, ending in a backslash (\).
18
19If crypt is available, files can be read and written using DES encryption.
20The `x' command prompts the user to enter a key used for encrypting/
21decrypting subsequent reads and writes.  If only a newline is entered as
22the key, then encryption is disabled.  Otherwise, a key is read in the
23same manner as a password entry.  The key remains in effect until
24encryption is disabled.  For more information on the encryption algorithm,
25see the bdes(1) man page.  Encryption/decryption should be fully compatible
26with SunOS DES.
27
28An extension to the POSIX file commands `E', `e', `r', `W' and `w' is that
29<file> arguments are processed for backslash escapes, i.e.,  any character
30preceded by a backslash is interpreted literally.  A trailing backslash
31is ignored.  If the first unescaped character of a <file> argument is a
32bang (!), then the rest of the line is interpreted as a shell command,
33and no escape processing is performed by ed.  This rule does not apply to
34the 'f' command (described below).
35
36While the default file name cannot be set to a shell command (i.e.,
37!<shell-cmd>) via any of the `r', `w', and `e' commands, POSIX evidently
38does not preclude using the `f' command for this purpose.  Upon reading
39or writing the default file when its name begins with a bang, ed
40interprets the rest of the line as a shell command and attempts to execute
41it.  Escape processing is not performed in this case.
42
43If ed is invoked with a name argument prefixed by a bang, then the
44remainder of the argument is interpreted as a shell command.  To invoke
45ed on a file whose name starts with bang, prefix the name with a backslash.
46--
47The following commands are neither part of POSIX 1003.2 D11/2 nor are
48they supported in this version of ed.
49
50The vi command: (addr1,addr2) !<shell-cmd> which replaces a range of
51lines with the output of a shell command is not supported.
52
53The vi command: [rwe] !!, where !! is replaced by the previous
54!<shell-cmd> is not supported.
55