1 12/2/84  forum request:  reply, rp
  2 
  3 Syntax:  rp {transaction_specifier} {-control_args}
  4 
  5 
  6 Function:
  7 Allows a participant to build, and optionally enter into the a meeting,
  8 a transaction which is in reply to an earlier transaction.
  9 
 10 
 11 Arguments:
 12 transaction_specifier
 13    is the transaction specifier of the transaction to be replied to.
 14    If this argument is not given, the current transaction is replied
 15    to.  Transaction specifier must name only one transaction, and
 16    therefore may not include a user_id, regular expression, or range.
 17 
 18 
 19 Control arguments:
 20 -auto_write
 21    Do not require the "w" request to be given in the editor
 22    in order to save editing changes. This is only meaningful
 23    if the transaction is entered from the terminal and ended
 24    with \f.
 25 -brief, -bf
 26    suppresses printing of the message indicating that the transaction
 27    was successfully entered.
 28 
 29 
 30 -fill, -fi
 31    specifies that the transaction should be filled after the user has
 32    exited input mode. This is the default, unless the -input_file
 33    control argument is used or unless the -no_input_fill (-nif)
 34    control argument was given with the invocation of forum.  The
 35    default fill width is 72, but the user can specify the fill width
 36    -via the line_length control argument or either the -line_length
 37    or -input_line_length control arguments to the forum command.
 38 -force, -fc
 39    overwrites a previous unprocessed transaction without querying.
 40 -input_file pathname, -if pathname
 41    specifies that the segment named by pathname be entered into the
 42    meeting. The default is to read the transaction from the terminal.
 43 
 44 
 45 -line_length LENGTH, -ll LENGTH
 46    fills the transaction to the specified line length.  The default
 47    is 72 columns unless a different value was given with the
 48    -input_line_length or -line_length control arguments to the forum
 49    command.
 50 -long, -lg
 51    print a message indicating that the transaction was successfully
 52    entered. (Default).
 53 -meeting meeting_name, -mtg meeting_name
 54    enters the transaction into the meeting_name meeting. The default
 55    is to enter the transaction into the proceedings of the meeting
 56    the user is currently attending. meeting_name may be a meeting name
 57    or a pathname.
 58 
 59 
 60 -no_auto_write
 61    Require the "w" request to be given in the editor
 62    in order to save editing changes. This is only meaningful
 63    if the transaction is entered from the terminal and ended
 64    with \f.  (Default)
 65 -no_fill, -nfi
 66    specifies that the transaction not be filled to the default fill
 67    width when entered.  The default is to fill the transaction, unless
 68    the -input_file control argument is specified or the -no_input_fill
 69    argument was given with the invocation of forum.  The default fill
 70    width is 72, but the user can specify the fill width via the
 71    -line_length control argument or either the -line_length
 72    or -input_line_length control arguments to the forum command.
 73 
 74 
 75 -no_force, -nfc
 76    query before overwriting a previous unprocessed transaction.
 77 -no_request_loop, -nrql
 78    causes the transaction to be entered into the meeting without first
 79    entering the forum request loop. (Default unless -if is given)
 80 -request_loop, -rql
 81    causes the forum request loop to be entered before the transaction
 82    is entered in the meeting. (Default if -if is given)
 83 -subject subject_string, -sj subject_string
 84    Specifies that subject_string be used as the subject, avoiding the
 85    prompt for subject. The default is to use the subject of the
 86    transaction being replied to. If subject_string contains whitespace,
 87    it must be quoted.
 88 -terminal_input, -ti
 89    Specifies that the transaction be input from the user's terminal.
 90    (Default)
 91 
 92 
 93 Notes on terminal input:
 94 Unless the user makes use of the -input_file control argument, the
 95 transaction will be built by taking lines from the user's terminal.
 96 There are three methods of exiting from terminal input mode -  line
 97 consisting of the single character period (.)
 98 
 99 Enters the transaction as is, returns to forum request level.
100 \f
101    exits terminal input mode and invokes 'qedx' editor on transaction.
102 \q or \fq
103    exits terminal input mode and enters forum request loop.
104 
105 
106 Notes:
107 A transaction which was not entered via the period (.) exit from
108 terminal input mode may be entered from forum request level via the
109 'enter' request.  Type 'help enter' from forum request level for
110 details.