1    /CONTINUOUS_PAGES

   /[NO]CONTINUOUS_PAGES

   Specify /CONTINUOUS_PAGES if you want pages separated by a form
   feed appended to the end of the last line of the page. This is
   useful when one wants to use all lines of a page, where the
   form-feed on a separate line could cause a page to be skipped
   between each page of text.

   Specify /NOCONTINUOUS_PAGES if you want pages separated by a
   form feed which is on a line by itself. This is the default.

2    /CURSOR_FLUSH

   /CURSOR_FLUSH=n

   Specify a line number which, if the cursor is positioned back
   to that line after being on a different line, the current
   screen contents will be flushed to the output file.

   This is useful for formatting screens which display data over
   the top of prior data, rather than clearing the screen before
   displaying the new data.

   The default value is zero. This means the cursor position
   is ignored.

   If specified as a negative number, this indicates that, if the
   cursor moves up that number of lines, the current screen
   contents will be flushed to the output file.

   Example:

     $ KERMIT                           ! Start program.
     Kermit-32> LOG SESSION PRICES.LOG  ! Start log file.
     Kermit-32> CONNECT TXA6:           ! Connect to modem line.
     ATDT-1-800-234-1998                ! Dial DEC's store.
     etc.
     $ PEEK /FORMAT PRICES.LOG PRICES.LIS /CURSOR_FLUSH=3

   When DEC's Electronic Store is accessed to look up prices,
   it positions to line 3, outputs a line of price information,
   then positions to line 4, etc., until the screen is full.

   When you tell it to display the next screen, it repeats this
   process. Using /CURSOR_FLUSH=3 tells the FORMAT command to
   output the prior screen before figuring out what the next
   screen will be.

3    /FORM_FEED

   /[NO]FORM_FEED

   Specify /FORM_FEED if you wish to have output pages separated
   by a form feed character. This is the default.

   Specify /NOFORM_FEED if you do not wish to have output pages
   separated by a form feed character.

4    /RECORD_END

   /[NO]RECORD_END

   PEEK/FORMAT tries to intelligently cope with log files which
   have overly-long lines which have been arbitrary split into
   more than one log-file record. This is most commonly
   encountered with Kermit log files, as covered in the
   PEEK Commands FORMAT Subtopic: Overview.

   The FORMAT /RECORD_END qualifier specifies that newlines
   should be inserted between records in the input file.

   This is the default for all input files, except those with
   variable-length, maximum 256-byte records and CR carriage-
   control. Kermit log files have this latter file format. For
   such files only, the default is /NORECORD_END.

   Specifying /NORECORD_END directs the FORMAT command not to
   insert a newline between records if the previous line ends at
   or before the screen's right margin.

   This commonly has the effect of concatenating all records in
   the input file into one continuous stream of input characters,
   without the FORMAT command adding any newlines.

   The presumption here is that the log-file contains in it the
   needed carriage-control characters, and none need to be added
   at the end of each log-file record.