rcsedit
Integrity Lifecycle Manager editing facilities for descriptions and log messages
Description
Whenever Integrity Lifecycle Manager asks you to enter a description or log message, you may make use of editing commands to help you enter the message. Editing commands must be on a separate line and the first character of the line must be a tilde ~ character. Here are the recognized commands:
• ~?
Displays a summary of editing commands.
• ~d
Restore message from dead.let file.
• ~e
Writes the current message to a temporary file and invokes a text editor to edit that file. The name of the editor is taken from the EDITOR environment variable. If there is no such variable, ed is used. When you are finished editing the message, write it back out to the temporary file and quit the editor. You return to Integrity Lifecycle Manager.
• ~p
Displays the current text of the message.
• ~q
Copies the current message to a file named dead.let and quits.
• ~r filename
Reads the contents of the given file and appends them to the current message.
• ~v
Similar to ~e, except that it invokes the visual editor identified by the VISUAL environment variable. The default is vi. (You can only use vi if you have a UNIX system or the MKS Toolkit.)
• ~w filename
Writes the current message to the specified file.
• ~! command
Executes the given system command.
If a line begins with a tilde, Integrity Lifecycle Manager assumes it is an editing command. If you want to enter a text line that begins with a tilde, type two, as in
~~ This line begins with a single tilde.
Examples
These are the changes I have made:
~r changes
.
reads in text from a file named changes and adds that text to the message being composed. The period (.) to mark the end of the message is still required.
Environment Variables
The Integrity Lifecycle Manager editing facilities use the following environment variables:
• EDITOR
contains the name of the editor invoked by the ~e command.
• VISUAL
contains the name of the editor invoked by the ~v command.
PORTABILITY
These facilities are extensions to traditional implementations of RCS and are non-portable.
See Also