i
ied(1) |
| ied(1) |
\t | tab | \v vertical tab |
\b | backspace |
|
Three- and
Many commands do not prompt when ready for input. | ied approximates a prompt- | ||
| ing mechanism for such commands. This is not always perfectly successful, but for | ||
| many commands it helps. In the worst case, the prompt is interspersed with output | ||
| in the wrong location. prompt is a string as used in the format argument to | ||
| printf(3S). The only % conversions that can be included are up to one instance of %d | ||
| which is converted to the sequential number of the command, and any number of | ||
| occurrences of %% which is treated as a literal % character. Prompting is suppressed | ||
| when ied is operating in transparent mode. |
| |
This sets | |||
| ing simple text. This causes ied to use tty line discipline most of the time. The | ||
| disadvantage of the default mode is that more context switches and general processing | ||
| are required. The advantage is that ied is more | transparent. For example, to | |
| speci®cally send an | ||
| acter (usually | ||
| function | ||
This option speci®es the size of the history buffer. When ied is started with an | |||
| existing history ®le, approximately the last size lines are available to the history | ||
| mechanism (the number is not guaranteed to be exactly size). Other lines in the ®le | ||
| are retained until such time as | ied is started on that history ®le and it exceeds | |
| approximately 4K bytes in size, | at which time ied discards older entries at the | |
| beginning of the ®le until it is near 4 Kbytes in size. Since this occurs only at startup, | ||
| history ®les can grow to be quite large between restarts. Larger values of size make | ||
| the process image larger. |
|
|
| If | ||
| If neither is speci®ed, a default is used. |
| |
Set transparent mode. This forces ied to permanently be in transparent mode (as | |||
| discussed above). It is primarily useful with | ||
| cessing. In particular, it is useful for driving a command if the command takes as | ||
| input what ied would interpret as editing characters. Thus with the appropriate | ||
| combinations of | ||
| smart application from a batch ®le. |
| |
Should something go wrong with ied, the SIGQUIT signal, repeated 3 times, usually aborts ied. The exception is the case of a fully transparent application, where ied must be killed from another window or terminal. This is really relevant only when there is no way to direct the serviced process to terminate itself.
The editing capabilities of ied are essentially those found in ksh. Only those that differ from ksh are described below. As in ksh, the style of editing is determined from the environment variable VISUAL, or from EDITOR if VISUAL is not speci®ed. The value examined should end in vi, emacs, or gmacs to specify an editor type. If it does not, ied does no editing, and history is not accessible.
In vi mode: |
|
|
J | Join lines. Considering the most recently edited line (which is empty immedi- | |
| ately after a line is sent to the application) to be the ``last line'' of the history, the | |
| current line being displayed from the history is appended to the end of the last | |
| line, and the position in the history is reset to be at the last line which is then | |
| displayed. A space is inserted between the old and new text on the last line. | |
| The cursor is left on that space. Because ied's understanding of line continua- | |
| tion is minimal, this is useful for editing long statements. | |
v | Not supported. |
|
V | Not supported. |
|
# | Sends nothing to the application, but inserts the line in the history (useful for | |
| adding comments to history ®le). |
|
Section 1−354 | − 2 − | |