Annotation of 43BSDReno/share/doc/usd/08.mh/prompter.me, revision 1.1.1.1

1.1       root        1: .\"    This file is automatically generated.  Do not edit!
                      2: .SC PROMPTER 1
                      3: .NA
                      4: prompter \- prompting editor front\-end
                      5: .SY
                      6: prompter
                      7: \%[\-erase\ chr]
                      8: \%[\-kill\ chr]
                      9: \%[\-prepend] \%[\-noprepend]
                     10: \%[\-rapid] \%[\-norapid]
                     11: file
                     12: \%[\-help]
                     13: .DE
                     14: This program is normally not invoked directly by users
                     15: but takes the place of an editor and acts as an editor front\-end.
                     16: It operates on an 822\-style message draft skeleton specified by file,
                     17: normally provided by \fIcomp\fR, \fIdist\fR, \fIforw\fR, or \fIrepl\fR.
                     18: 
                     19: \fIPrompter\fR is an editor which allows rapid composition of
                     20: messages.
                     21: It is particularly useful to network and low\-speed
                     22: (less than 2400 baud) users of \fIMH\fR.
                     23: It is an \fIMH\fR program in that
                     24: it can have its own profile entry with switches,
                     25: but it is not invoked directly by the user.
                     26: The commands \fIcomp\fR, \fIdist\fR, \fIforw\fR, and \fIrepl\fR
                     27: invoke \fIprompter\fR as an editor,
                     28: either when invoked with `\-editor\ prompter',
                     29: or by the profile entry \*(lqEditor:\ prompter\*(rq,
                     30: or when given the command `edit\ prompter' at \*(lqWhat now?\*(rq level.
                     31: 
                     32: For each empty component \fIprompter\fR finds in the draft,
                     33: the user is prompted for a response;
                     34: A <RETURN> will cause the whole component to be left out.
                     35: Otherwise,
                     36: a `\\' preceding a <RETURN> will continue the response on the next line,
                     37: allowing for multiline components.
                     38: Continuation lines \fBmust\fR begin with a space or tab.
                     39: 
                     40: Each non\-empty component is copied to the draft and displayed on the
                     41: terminal.
                     42: 
                     43: The start of the message body is denoted by a blank line or a line of dashes.
                     44: If the body is non\-empty, the prompt, which isn't written to the file, is
                     45: 
                     46:     \*(lq--------Enter additional text\*(rq,
                     47: 
                     48: or (if `\-prepend' was given)
                     49: 
                     50:     \*(lq--------Enter initial text\*(rq.
                     51: 
                     52: Message\-body typing is terminated with an end\-of\-file (usually CTRL\-D).
                     53: At this point control is returned to the calling program,
                     54: where the user is asked \*(lqWhat now?\*(rq.
                     55: See \fIwhatnow\fR for the valid options to this query.
                     56: 
                     57: By using the `\-prepend' switch, the user can add type\-in to the beginning
                     58: of the message body and have the rest of the body follow.
                     59: This is useful for the \fIforw\fR command.
                     60: 
                     61: By using the `\-rapid' switch,
                     62: if the draft already contains text in the message\-body,
                     63: it is not displayed on the user's terminal.
                     64: This is useful for low\-speed terminals.
                     65: 
                     66: The line editing characters for kill and erase may be
                     67: specified by the user via the arguments `\-kill\ chr' and `\-erase\ chr',
                     68: where chr may be a character; or `\\nnn', where \*(lqnnn\*(rq is the
                     69: octal value for the character.
                     70: 
                     71: An interrupt (usually CTRL\-C) during component typing will abort
                     72: \fIprompter\fR and the \fIMH\fR command that invoked it.
                     73: An interrupt during message\-body typing is equivalent to CTRL\-D,
                     74: for historical reasons.
                     75: This means that \fIprompter\fR should finish up and exit.
                     76: 
                     77: The first non\-flag argument to \fIprompter\fR
                     78: is taken as the name of the draft file, and
                     79: subsequent non\-flag arguments are ignored.
                     80: .\" (\fIRepl\fR invokes editors with two file arguments:
                     81: .\" the draft file name and the replied\-to message file name.)
                     82: .Fi
                     83: ^$HOME/\&.mh\(ruprofile~^The user profile
                     84: ^/tmp/prompter*~^Temporary copy of message
                     85: .Pr
                     86: prompter\-next:        To name the editor to be used on exit from \fIprompter\fR
                     87: .Ps
                     88: ^Msg\-Protect:~^To set mode when creating a new draft
                     89: .Sa
                     90: comp(1), dist(1), forw(1), repl(1), whatnow(1)
                     91: .De
                     92: `\-prepend'
                     93: .Ds
                     94: `\-norapid'
                     95: .Co
                     96: None
                     97: .Bu
                     98: \fIPrompter\fR uses \fIstdio\fR\0(3), so it will lose if you edit files
                     99: with nulls in them.
                    100: .En

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.