From 5328ae3ad39eef3632f83c670e0035f924bfe0d8 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Thu, 6 Jun 2019 17:32:22 -0700 Subject: [PATCH 1/1] doc: Better describe the effect of OUTFILE on PRINT. Reported by Nolan Void . --- doc/data-io.texi | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/data-io.texi b/doc/data-io.texi index 9341a58c8a..1d1f13e362 100644 --- a/doc/data-io.texi +++ b/doc/data-io.texi @@ -1152,9 +1152,10 @@ are specified, @cmd{PRINT} outputs a single blank line. The @subcmd{OUTFILE} subcommand specifies the file to receive the output. The file may be a file name as a string or a file handle (@pxref{File Handles}). If @subcmd{OUTFILE} is not present then output will be sent to -@pspp{}'s output listing file. When @subcmd{OUTFILE} is present, a space is -inserted at beginning of each output line, even lines that otherwise -would be blank. +@pspp{}'s output listing file. When @subcmd{OUTFILE} is present, the +output is written to @var{file_name} in a plain text format, with a +space inserted at beginning of each output line, even lines that +otherwise would be blank. The @subcmd{ENCODING} subcommand may only be used if the @subcmd{OUTFILE} subcommand is also used. It specifies the character -- 2.30.2