+2007-06-05 Ben Pfaff <blp@gnu.org>
+
+ * Removed next, prev, up node names from @node lines, to make
+ structural changes to the manual easier. (These node names are
+ not needed by makeinfo.)
+
2007-03-31 John Darrington <john@darrington.wattle.id.au>
* transformation.texi: SORT CASES: elaborated on the (D) (A) flags.
-@node Bugs, Function Index, Not Implemented, Top
+@node Bugs
@chapter Bugs
PSPP does have bugs. We do our best to fix them, but our limited
-@node Command Index, Concept Index, Function Index, Top
+@node Command Index
@chapter Command Index
@printindex vr
@setfilename ignored
-@node Concept Index, Configuration, Command Index, Top
+@node Concept Index
@chapter Concept Index
@printindex cp
@setfilename ignored
-@node Configuration, Portable File Format, Concept Index, Top
+@node Configuration
@appendix Configuring PSPP
@cindex configuration
@cindex PSPP, configuring
* Miscellaneous configuring:: Even more configuration variables.
@end menu
-@node File locations, Configuration techniques, Configuration, Configuration
+@node File locations
@section Locating configuration files
PSPP searches each directory in the configuration file path for most
@samp{--config-dir=@var{path}} specified on the command line has highest
priority.
-@node Configuration techniques, Configuration files, File locations, Configuration
+@node Configuration techniques
@section Configuration techniques
There are many ways that PSPP can be configured. These are
Some of the above may not apply to a particular setting.
-@node Configuration files, Environment variables, Configuration techniques, Configuration
+@node Configuration files
@section Configuration files
Most configuration files have a common form:
Blank lines, and lines that contain only white space, are ignored.
@end itemize
-@node Environment variables, Output devices, Configuration files, Configuration
+@node Environment variables
@section Environment variables
You may think the concept of environment variables is a fairly simple
* Predefined variables:: A few variables are automatically defined.
@end menu
-@node Environment substitutions, Predefined variables, Environment variables, Environment variables
+@node Environment substitutions
@subsection Environment substitutions
Much of the power of environment variables lies in the way that they may
Undefined variables expand to a empty value.
-@node Predefined variables, , Environment substitutions, Environment variables
+@node Predefined variables
@subsection Predefined environment variables
There are two environment variables predefined for use in environment
Nothing prevents these values from being overridden, although it's a
good idea not to do so.
-@node Output devices, PostScript driver class, Environment variables, Configuration
+@node Output devices
@section Output devices
Configuring output devices is the most complicated aspect of configuring
* Tokenizing lines:: Dividing @file{devices} lines into tokens.
@end menu
-@node Driver categories, Macro definitions, Output devices, Output devices
+@node Driver categories
@subsection Driver categories
Drivers can be divided into categories. Drivers are specified by their
It is an error if the list is not empty when the end of @file{devices}
is reached.
-@node Macro definitions, Device definitions, Driver categories, Output devices
+@node Macro definitions
@subsection Macro definitions
Macro definitions take the form @samp{define @var{macroname}
@end table
@end itemize
-@node Device definitions, Dimensions, Macro definitions, Output devices
+@node Device definitions
@subsection Driver definitions
Driver definitions are the ultimate purpose of the @file{devices}
Options are dependent on the driver. See the driver descriptions for
details.
-@node Dimensions, papersize, Device definitions, Output devices
+@node Dimensions
@subsection Dimensions
Quite often in configuration it is necessary to specify a length or a
@end itemize
@end itemize
-@node papersize, Distinguishing line types, Dimensions, Output devices
+@node papersize
@subsection Paper sizes
Output drivers usually deal with some sort of hardcopy media. This
search becomes paper name @var{paper-2} and the search through the file
continues.
-@node Distinguishing line types, Tokenizing lines, papersize, Output devices
+@node Distinguishing line types
@subsection How lines are divided into types
The lines in @file{devices} are distinguished in the following manner:
Otherwise, the line is ill-formed.
@end enumerate
-@node Tokenizing lines, , Distinguishing line types, Output devices
+@node Tokenizing lines
@subsection How lines are divided into tokens
Each driver definition line is run through a simple tokenizer. This
Tokens, outside of quoted strings, are delimited by white space or equals
signs.
-@node PostScript driver class, ASCII driver class, Output devices, Configuration
+@node PostScript driver class
@section The PostScript driver class
The @code{postscript} driver class is used to produce output that is
Sets the width of the lines used in tables. Default: @code{0.5pt}.
@end table
-@node ASCII driver class, HTML driver class, PostScript driver class, Configuration
+@node ASCII driver class
@section The ASCII driver class
The ASCII driver class produces output that can be displayed on a
you might pass the output.
@end table
-@node HTML driver class, Miscellaneous configuring, ASCII driver class, Configuration
+@node HTML driver class
@section The HTML driver class
The @code{html} driver class is used to produce output for viewing in
the chart number. Default: @file{"pspp-#.png"}.
@end table
-@node Miscellaneous configuring,, HTML driver class, Configuration
+@node Miscellaneous configuring
@section Miscellaneous configuration
The following environment variables can be used to further configure
-@node Data File Format, q2c Input Format, Portable File Format, Top
+@node Data File Format
@appendix Data File Format
PSPP necessarily uses the same format for system files as do the
* Data Record::
@end menu
-@node File Header Record, Variable Record, Data File Format, Data File Format
+@node File Header Record
@section File Header Record
The file header is always the first record in the file.
length. Set to zeros.
@end table
-@node Variable Record, Value Label Record, File Header Record, Data File Format
+@node Variable Record
@section Variable Record
Immediately following the header must come the variable records. There
@code{SDATE}
@end table
-@node Value Label Record, Value Label Variable Record, Variable Record, Data File Format
+@node Value Label Record
@section Value Label Record
Value label records must follow the variable records and must precede
label. The remainder of the field is the label itself. The field is
padded on the right to a multiple of 64 bits in length.
-@node Value Label Variable Record, Document Record, Value Label Record, Data File Format
+@node Value Label Variable Record
@section Value Label Variable Record
Every value label variable record must be immediately preceded by a
to occupy multiple indexes.
@end table
-@node Document Record, Machine int32 Info Record, Value Label Variable Record, Data File Format
+@node Document Record
@section Document Record
There must be no more than one document record per system file.
Lines shorter than 80 characters are padded on the right with spaces.
@end table
-@node Machine int32 Info Record, Machine flt64 Info Record, Document Record, Data File Format
+@node Machine int32 Info Record
@section Machine @code{int32} Info Record
There must be no more than one machine @code{int32} info record per
Windows code page numbers are also valid.
@end table
-@node Machine flt64 Info Record, Auxiliary Variable Parameter Record, Machine int32 Info Record, Data File Format
+@node Machine flt64 Info Record
@section Machine @code{flt64} Info Record
There must be no more than one machine @code{flt64} info record per
The value used for LOWEST in missing values.
@end table
-@node Auxiliary Variable Parameter Record, Long Variable Names Record, Machine flt64 Info Record, Data File Format
+@node Auxiliary Variable Parameter Record
@section Auxiliary Variable Parameter Record
There must be no more than one auxiliary variable parameter record per
-@node Long Variable Names Record, Very Long String Length Record, Auxiliary Variable Parameter Record, Data File Format
+@node Long Variable Names Record
@section Long Variable Names Record
There must be no more than one long variable names record per
The total length is @code{count} bytes.
@end table
-@node Very Long String Length Record, Miscellaneous Informational Records, Long Variable Names Record, Data File Format
+@node Very Long String Length Record
@comment node-name, next, previous, up
@section Very Long String Length Record
-@node Miscellaneous Informational Records, Dictionary Termination Record, Very Long String Length Record, Data File Format
+@node Miscellaneous Informational Records
@section Miscellaneous Informational Records
Miscellaneous informational records must follow the variable records and
data.
@end table
-@node Dictionary Termination Record, Data Record, Miscellaneous Informational Records, Data File Format
+@node Dictionary Termination Record
@section Dictionary Termination Record
The dictionary termination record must follow all other records, except
Ignored padding. Should be set to 0.
@end table
-@node Data Record, , Dictionary Termination Record, Data File Format
+@node Data Record
@section Data Record
Data records must follow all other records in the data file. There must
-@node Data Input and Output, System and Portable Files, Expressions, Top
+@node Data Input and Output
@chapter Data Input and Output
@cindex input
@cindex output
-@node Data Selection, Conditionals and Looping, Data Manipulation, Top
+@node Data Selection
@chapter Selecting data for analysis
This chapter documents PSPP commands that temporarily or permanently
* WEIGHT:: Weight cases by a variable.
@end menu
-@node FILTER, N OF CASES, Data Selection, Data Selection
+@node FILTER
@section FILTER
@vindex FILTER
differing endianness or floating-point formats. By default, the
random number seed is based on the system time.
-@node SELECT IF, SPLIT FILE, SAMPLE, Data Selection
+@node SELECT IF
@section SELECT IF
@vindex SELECT IF
(@pxref{TEMPORARY}), the @cmd{LAG} function may not be used
(@pxref{LAG}).
-@node SPLIT FILE, TEMPORARY, SELECT IF, Data Selection
+@node SPLIT FILE
@section SPLIT FILE
@vindex SPLIT FILE
When @cmd{SPLIT FILE} is specified after @cmd{TEMPORARY}, it affects only
the next procedure (@pxref{TEMPORARY}).
-@node TEMPORARY, WEIGHT, SPLIT FILE, Data Selection
+@node TEMPORARY
@section TEMPORARY
@vindex TEMPORARY
10.5, 13, 15. The data read by the first @cmd{DESCRIPTIVES} are 1, 2,
5, 7.5, 10, 12.
-@node WEIGHT, , TEMPORARY, Data Selection
+@node WEIGHT
@section WEIGHT
@vindex WEIGHT
-@node Expressions, Data Input and Output, Language, Top
+@node Expressions
@chapter Mathematical Expressions
@cindex expressions, mathematical
@cindex mathematical expressions
-@node GNU Free Documentation License, , q2c Input Format, Top
+@node GNU Free Documentation License
@appendix GNU Free Documentation License
@cindex FDL, GNU Free Documentation License
-@node System and Portable Files, Variable Attributes, Data Input and Output, Top
+@node System and Portable Files
@chapter System Files and Portable Files
The commands in this chapter read, write, and examine system files and
@xref{EXPORT}, for more information.
-@node XSAVE, , XEXPORT, System and Portable Files
+@node XSAVE
@section XSAVE
@vindex XSAVE
-@node Conditionals and Looping, Statistics, Data Selection, Top
+@node Conditionals and Looping
@chapter Conditional and Looping Constructs
@cindex conditionals
@cindex loops
* LOOP:: Repeat a block of code.
@end menu
-@node BREAK, DO IF, Conditionals and Looping, Conditionals and Looping
+@node BREAK
@section BREAK
@vindex BREAK
@cmd{BREAK} is allowed only inside @cmd{LOOP}@dots{}@cmd{END LOOP}.
@xref{LOOP}, for more details.
-@node DO IF, DO REPEAT, BREAK, Conditionals and Looping
+@node DO IF
@section DO IF
@vindex DO IF
(@pxref{TEMPORARY}), the @cmd{LAG} function may not be used
(@pxref{LAG}).
-@node DO REPEAT, LOOP, DO IF, Conditionals and Looping
+@node DO REPEAT
@section DO REPEAT
@vindex DO REPEAT
are made are printed to the listing file, prefixed by a plus sign
(@samp{+}).
-@node LOOP, , DO REPEAT, Conditionals and Looping
+@node LOOP
@section LOOP
@vindex LOOP
-@node Function Index, Command Index, Bugs, Top
+@node Function Index
@chapter Function Index
@printindex fn
@setfilename ignored
-@node Installation, Configuration, Concept Index, Top
+@node Installation
@appendix Installing PSPP
@cindex installation
@cindex PSPP, installing
-@node Introduction, License, Top, Top
+@node Introduction
@chapter Introduction
@cindex introduction
-@node Invocation, Language, License, Top
+@node Invocation
@chapter Invoking PSPP
@cindex invocation
@cindex PSPP, invoking
* Informational options:: Helpful information about PSPP.
@end menu
-@node Non-option Arguments, Configuration Options, Invocation, Invocation
+@node Non-option Arguments
@section Non-option Arguments
Syntax files and output device substitutions can be specified on
typing its name. You can include any options on the command line as
usual. PSPP entirely ignores any lines beginning with @samp{#!}.
-@node Configuration Options, Input and output options, Non-option Arguments, Invocation
+@node Configuration Options
@section Configuration Options
Configuration options are used to change PSPP's configuration for the
option disables all devices besides those mentioned on the command line.
@end table
-@node Input and output options, Language control options, Configuration Options, Invocation
+@node Input and output options
@section Input and output options
Input and output options affect how PSPP reads input and writes
check} and similar scripts.
@end table
-@node Language control options, Informational options, Input and output options, Invocation
+@node Language control options
@section Language control options
Language control options control how PSPP syntax files are parsed and
HOST commands, as well as use of pipes as input and output files.
@end table
-@node Informational options, , Language control options, Invocation
+@node Informational options
@section Informational options
Informational options cause information about PSPP to be written to
-@node Language, Expressions, Invocation, Top
+@node Language
@chapter The PSPP language
@cindex language, PSPP
@cindex PSPP, language
* BNF:: How command syntax is described.
@end menu
-@node Tokens, Commands, Language, Language
+@node Tokens
@section Tokens
@cindex language, lexical analysis
@cindex language, tokens
the default setting is in effect.
@end table
-@node Commands, Types of Commands, Tokens, Language
+@node Commands
@section Forming commands of tokens
@cindex PSPP, command structure
which allows for visual indentation of a command without that command
being considered part of the previous command.
-@node Types of Commands, Order of Commands, Commands, Language
+@node Types of Commands
@section Types of Commands
Commands in PSPP are divided roughly into six categories:
active file (the data) to be read.
@end table
-@node Order of Commands, Missing Observations, Types of Commands, Language
+@node Order of Commands
@section Order of Commands
@cindex commands, ordering
@cindex order of commands
@end itemize
@end table
-@node Missing Observations, Variables, Order of Commands, Language
+@node Missing Observations
@section Handling missing observations
@cindex missing values
@cindex values, missing
documentation on individual procedures for information on how they
handle missing values.
-@node Variables, Files, Missing Observations, Language
+@node Variables
@section Variables
@cindex variables
@cindex dictionary
* Scratch Variables:: Variables deleted by procedures.
@end menu
-@node Attributes, System Variables, Variables, Variables
+@node Attributes
@subsection Attributes of Variables
@cindex variables, attributes of
@cindex attributes of variables
(@pxref{WRITE}).
@end table
-@node System Variables, Sets of Variables, Attributes, Variables
+@node System Variables
@subsection Variables Automatically Defined by PSPP
@cindex system variables
@cindex variables, system
Page width, in characters, in format F3.
@end table
-@node Sets of Variables, Input and Output Formats, System Variables, Variables
+@node Sets of Variables
@subsection Lists of variable names
@cindex @code{TO} convention
@cindex convention, @code{TO}
another command with this method, the same set can be referenced on
later commands using the same syntax.
-@node Input and Output Formats, Scratch Variables, Sets of Variables, Variables
+@node Input and Output Formats
@subsection Input and Output Formats
@cindex formats
input, uppercase and lowercase are both accepted. The default output
format is A format with half the input width.
-@node Scratch Variables, , Input and Output Formats, Variables
+@node Scratch Variables
@subsection Scratch Variables
@cindex scratch variables
-@node License, Invocation, Introduction, Top
+@node License
@chapter Your rights and obligations
@cindex license
@cindex licence
-@node Not Implemented, Bugs, Utilities, Top
+@node Not Implemented
@chapter Not Implemented
This chapter lists parts of the PSPP language that are not yet
-@node Portable File Format, Data File Format, Configuration, Top
+@node Portable File Format
@appendix Portable File Format
These days, most computers use the same internal data formats for
* Portable File Data::
@end menu
-@node Portable File Characters, Portable File Structure, Portable File Format, Portable File Format
+@node Portable File Characters
@section Portable File Characters
Portable files are arranged as a series of lines of exactly 80
because they are not an important part of understanding the file
contents.
-@node Portable File Structure, Portable File Header, Portable File Characters, Portable File Format
+@node Portable File Structure
@section Portable File Structure
Every portable file consists of the following records, in sequence:
String fields take the form of a integer field having value @var{n},
followed by exactly @var{n} characters, which are the string content.
-@node Portable File Header, Version and Date Info Record, Portable File Structure, Portable File Format
+@node Portable File Header
@section Portable File Header
Every portable file begins with a 464-byte header, consisting of a
in the portable file's character set, which can be used to verify that
the file is indeed a portable file.
-@node Version and Date Info Record, Identification Records, Portable File Header, Portable File Format
+@node Version and Date Info Record
@section Version and Date Info Record
This record does not have a tag code. It has the following structure:
HHMMSS.
@end itemize
-@node Identification Records, Variable Count Record, Version and Date Info Record, Portable File Format
+@node Identification Records
@section Identification Records
The product identification record has tag code @samp{1}. It consists of
optional. If present, it consists of a single string field giving
additional information on the product that wrote the portable file.
-@node Variable Count Record, Case Weight Variable Record, Identification Records, Portable File Format
+@node Variable Count Record
@section Variable Count Record
The variable count record has tag code @samp{4}. It consists of two
dictionary. The purpose of the second is unknown; it contains the value
161 in all portable files examined so far.
-@node Case Weight Variable Record, Variable Records, Variable Count Record, Portable File Format
+@node Case Weight Variable Record
@section Case Weight Variable Record
The case weight variable record is optional. If it is present, it
cases are unweighted. It has tag code @samp{6}. It consists of a
single string field that names the weighting variable.
-@node Variable Records, Value Label Records, Case Weight Variable Record, Portable File Format
+@node Variable Records
@section Variable Records
Each variable record represents a single variable. Variable records
variable label record, which has tag code @samp{C}. A variable label
record has one field, the variable label itself (string).
-@node Value Label Records, Portable File Data, Variable Records, Portable File Format
+@node Value Label Records
@section Value Label Records
Value label records have tag code @samp{D}. They have the following
appropriate to the variables, followed by a label (string).
@end itemize
-@node Portable File Data, , Value Label Records, Portable File Format
+@node Portable File Data
@section Portable File Data
The data record has tag code @samp{F}. There is only one tag for all
-@node q2c Input Format, GNU Free Documentation License, Data File Format, Top
+@node q2c Input Format
@appendix @code{q2c} Input Format
PSPP statistical procedures have a bizarre and somewhat irregular
* Grammar Rules:: Syntax of the grammar rules.
@end menu
-@node Invoking q2c, q2c Input Structure, q2c Input Format, q2c Input Format
+@node Invoking q2c
@section Invoking q2c
@example
output file name, respectively. @code{q2c} does not accept any
command-line options.
-@node q2c Input Structure, Grammar Rules, Invoking q2c, q2c Input Format
+@node q2c Input Structure
@section @code{q2c} Input Structure
@code{q2c} input files are divided into two sections: the grammar rules
@code{string} are used in the grammar rules.
@end table
-@node Grammar Rules, , q2c Input Structure, q2c Input Format
+@node Grammar Rules
@section Grammar Rules
The grammar rules describe the format of the syntax that the parser
-@node REGRESSION, ,RANK, Statistics
+@node REGRESSION
@comment node-name, next, previous, up
@section REGRESSION
* Examples:: Using the REGRESSION procedure.
@end menu
-@node Syntax, Examples, , REGRESSION
+@node Syntax
@subsection Syntax
@vindex REGRESSION
program and use it as part of another program. This subcommand is a
PSPP extension.
-@node Examples, , Syntax, REGRESSION
+@node Examples
@subsection Examples
The following PSPP syntax will generate the default output, save the
predicted values and residuals to the active file, and save the
-@node Statistics, Utilities, Conditionals and Looping, Top
+@node Statistics
@chapter Statistics
This chapter documents the statistical procedures that PSPP supports so
* REGRESSION:: Linear regression.
@end menu
-@node DESCRIPTIVES, FREQUENCIES, Statistics, Statistics
+@node DESCRIPTIVES
@section DESCRIPTIVES
@vindex DESCRIPTIVES
and D settings request an ascending or descending sort order,
respectively.
-@node FREQUENCIES, EXAMINE, DESCRIPTIVES, Statistics
+@node FREQUENCIES
@section FREQUENCIES
@vindex FREQUENCIES
displayed slices to a given range of values. The MISSING keyword adds
slices for missing values.
-@node EXAMINE, CROSSTABS, FREQUENCIES, Statistics
+@node EXAMINE
@comment node-name, next, previous, up
@section EXAMINE
@vindex EXAMINE
large quantity of output.
-@node CROSSTABS, NPAR TESTS, EXAMINE, Statistics
+@node CROSSTABS
@section CROSSTABS
@vindex CROSSTABS
Fixes for any of these deficiencies would be welcomed.
-@node NPAR TESTS, T-TEST, CROSSTABS, Statistics
+@node NPAR TESTS
@section NPAR TESTS
@vindex NPAR TESTS
@end menu
-@node BINOMIAL, CHISQUARE, NPAR TESTS, NPAR TESTS
+@node BINOMIAL
@subsection Binomial test
@vindex BINOMIAL
@cindex binomial test
-@node CHISQUARE, , BINOMIAL, NPAR TESTS
+@node CHISQUARE
@subsection Chisquare test
@vindex CHISQUARE
@cindex chisquare test
are expected.
-@node T-TEST, ONEWAY, NPAR TESTS, Statistics
+@node T-TEST
@comment node-name, next, previous, up
@section T-TEST
* Paired Samples Mode:: Testing two interdependent groups for equal mean
@end menu
-@node One Sample Mode, Independent Samples Mode, T-TEST, T-TEST
+@node One Sample Mode
@subsection One Sample Mode
The @cmd{TESTVAL} subcommand invokes the One Sample mode.
In this mode, you must also use the @cmd{/VARIABLES} subcommand to
tell PSPP which variables you wish to test.
-@node Independent Samples Mode, Paired Samples Mode, One Sample Mode, T-TEST
+@node Independent Samples Mode
@comment node-name, next, previous, up
@subsection Independent Samples Mode
of whether @cmd{/MISSING=LISTWISE} was specified.
-@node Paired Samples Mode, , Independent Samples Mode, T-TEST
+@node Paired Samples Mode
@comment node-name, next, previous, up
@subsection Paired Samples Mode
@code{WITH} are generated.
-@node ONEWAY, RANK, T-TEST, Statistics
+@node ONEWAY
@comment node-name, next, previous, up
@section ONEWAY
to specify different contrast tests.
@setfilename ignored
-@node RANK, REGRESSION, ONEWAY, Statistics
+@node RANK
@comment node-name, next, previous, up
@section RANK
-@node Data Manipulation, Data Selection, Variable Attributes, Top
+@node Data Manipulation
@chapter Data transformations
@cindex transformations
* SORT CASES:: Sort the active file.
@end menu
-@node AGGREGATE, AUTORECODE, Data Manipulation, Data Manipulation
+@node AGGREGATE
@section AGGREGATE
@vindex AGGREGATE
@cmd{AGGREGATE} both ignores and cancels the current @cmd{SPLIT FILE}
settings (@pxref{SPLIT FILE}).
-@node AUTORECODE, COMPUTE, AGGREGATE, Data Manipulation
+@node AUTORECODE
@section AUTORECODE
@vindex AUTORECODE
@cmd{AUTORECODE} is a procedure. It causes the data to be read.
-@node COMPUTE, COUNT, AUTORECODE, Data Manipulation
+@node COMPUTE
@section COMPUTE
@vindex COMPUTE
(@pxref{TEMPORARY}), the @cmd{LAG} function may not be used
(@pxref{LAG}).
-@node COUNT, FLIP, COMPUTE, Data Manipulation
+@node COUNT
@section COUNT
@vindex COUNT
@end example
@end enumerate
-@node FLIP, IF, COUNT, Data Manipulation
+@node FLIP
@section FLIP
@vindex FLIP
@cmd{TEMPORARY} (@pxref{TEMPORARY}), so that ``temporary''
transformations become permanent.
-@node IF, RECODE, FLIP, Data Manipulation
+@node IF
@section IF
@vindex IF
(@pxref{TEMPORARY}), the @cmd{LAG} function may not be used
(@pxref{LAG}).
-@node RECODE, SORT CASES, IF, Data Manipulation
+@node RECODE
@section RECODE
@vindex RECODE
Introduce additional recodings with a slash (@samp{/}) to
separate them from the previous recodings.
-@node SORT CASES, , RECODE, Data Manipulation
+@node SORT CASES
@section SORT CASES
@vindex SORT CASES
-@node Utilities, Not Implemented, Statistics, Top
+@node Utilities
@chapter Utilities
Commands that don't fit any other category are placed here.
-@node COMMENT, DOCUMENT, ADD DOCUMENT, Utilities
+@node COMMENT
@section COMMENT
@vindex COMMENT
@vindex *
-@node DOCUMENT, DISPLAY DOCUMENTS, COMMENT, Utilities
+@node DOCUMENT
@section DOCUMENT
@vindex DOCUMENT
Lines are truncated at 80 bytes. Don't forget to terminate
the command with a dot or a blank line. @xref{ADD DOCUMENT}.
-@node DISPLAY DOCUMENTS, DISPLAY FILE LABEL, DOCUMENT, Utilities
+@node DISPLAY DOCUMENTS
@section DISPLAY DOCUMENTS
@vindex DISPLAY DOCUMENTS
document is preceded by a line giving the time and date that it was
added. @xref{DOCUMENT}.
-@node DISPLAY FILE LABEL, DROP DOCUMENTS, DISPLAY DOCUMENTS, Utilities
+@node DISPLAY FILE LABEL
@section DISPLAY FILE LABEL
@vindex DISPLAY FILE LABEL
This command is a PSPP extension.
-@node DROP DOCUMENTS, ECHO, DISPLAY FILE LABEL, Utilities
+@node DROP DOCUMENTS
@section DROP DOCUMENTS
@vindex DROP DOCUMENTS
@cmd{DROP DOCUMENTS} changes only the active file. It does not modify any
system files stored on disk.
-@node ECHO, ERASE, DROP DOCUMENTS, Utilities
+@node ECHO
@section ECHO
@vindex ECHO
Use @cmd{ECHO} to write arbitrary text to the output stream. The text should be enclosed in quotation marks following the normal rules for string tokens (@pxref{Tokens}).
-@node ERASE, EXECUTE, ECHO, Utilities
+@node ERASE
@comment node-name, next, previous, up
@section ERASE
@vindex ERASE
This command cannot be used if the SAFER setting is active.
-@node EXECUTE, FILE LABEL, ERASE, Utilities
+@node EXECUTE
@section EXECUTE
@vindex EXECUTE
@cmd{EXECUTE} causes the active file to be read and all pending
transformations to be executed.
-@node FILE LABEL, FINISH, EXECUTE, Utilities
+@node FILE LABEL
@section FILE LABEL
@vindex FILE LABEL
file_label need not be quoted. If quotes are
included, they become part of the file label.
-@node FINISH, HOST, FILE LABEL, Utilities
+@node FINISH
@section FINISH
@vindex FINISH
@cmd{FINISH} terminates the current PSPP session and returns
control to the operating system.
-@node HOST, INCLUDE, FINISH, Utilities
+@node HOST
@comment node-name, next, previous, up
@section HOST
@vindex HOST
This command cannot be used if the SAFER setting is active.
-@node INCLUDE, PERMISSIONS, HOST, Utilities
+@node INCLUDE
@section INCLUDE
@vindex INCLUDE
@vindex @@
Include files may be nested to any depth, up to the limit of available
memory.
-@node PERMISSIONS, SET, INCLUDE, Utilities
+@node PERMISSIONS
@comment node-name, next, previous, up
@section PERMISSIONS
@vindex PERMISSIONS
This command cannot be used if the SAFER setting is active.
-@node SET, SHOW, PERMISSIONS, Utilities
+@node SET
@section SET
@vindex SET
obvious security reasons.
@end table
-@node SHOW, SUBTITLE, SET, Utilities
+@node SHOW
@comment node-name, next, previous, up
@section SHOW
@vindex SHOW
Specifying @cmd{SHOW} without any subcommands is equivalent to SHOW ALL.
-@node SUBTITLE, TITLE, SHOW, Utilities
+@node SUBTITLE
@section SUBTITLE
@vindex SUBTITLE
not require quotes is now obsolete. If it is used then the subtitle is
converted to all uppercase.
-@node TITLE, , SUBTITLE, Utilities
+@node TITLE
@section TITLE
@vindex TITLE
-@node Variable Attributes, Data Manipulation, System and Portable Files, Top
+@node Variable Attributes
@chapter Manipulating variables
The variables in the active file dictionary are important. There are
* WRITE FORMATS:: Set variable write formats.
@end menu
-@node ADD VALUE LABELS, DELETE VARIABLES, Variable Attributes, Variable Attributes
+@node ADD VALUE LABELS
@section ADD VALUE LABELS
@vindex ADD VALUE LABELS
LABELS} (@pxref{VALUE LABELS}), but it does not clear value
labels from the variables before adding the ones specified.
-@node DELETE VARIABLES, DISPLAY, ADD VALUE LABELS, Variable Attributes
+@node DELETE VARIABLES
@section DELETE VARIABLES
@vindex DELETE VARIABLES
causes the data to be read. If it is used while @cmd{TEMPORARY} is in
effect, it causes the temporary transformations to become permanent.
-@node DISPLAY, DISPLAY VECTORS, DELETE VARIABLES, Variable Attributes
+@node DISPLAY
@section DISPLAY
@vindex DISPLAY
order based on their names; otherwise, they are displayed in the order
that they occur in the active file dictionary.
-@node DISPLAY VECTORS, FORMATS, DISPLAY, Variable Attributes
+@node DISPLAY VECTORS
@section DISPLAY VECTORS
@vindex DISPLAY VECTORS
@cmd{DISPLAY VECTORS} lists all the currently declared vectors.
-@node FORMATS, LEAVE, DISPLAY VECTORS, Variable Attributes
+@node FORMATS
@section FORMATS
@vindex FORMATS
@cmd{FORMATS} takes effect immediately. It is not affected by
conditional and looping structures such as @cmd{DO IF} or @cmd{LOOP}.
-@node LEAVE, MISSING VALUES, FORMATS, Variable Attributes
+@node LEAVE
@section LEAVE
@vindex LEAVE
certain transformations---for instance, @cmd{COMPUTE} and @cmd{IF}.
Left status is also reset by all procedure invocations.
-@node MISSING VALUES, MODIFY VARS, LEAVE, Variable Attributes
+@node MISSING VALUES
@section MISSING VALUES
@vindex MISSING VALUES
affected by conditional and looping constructs such as @cmd{DO IF} or
@cmd{LOOP}.
-@node MODIFY VARS, NUMERIC, MISSING VALUES, Variable Attributes
+@node MODIFY VARS
@section MODIFY VARS
@vindex MODIFY VARS
@cmd{MODIFY VARS} may not be specified following @cmd{TEMPORARY}
(@pxref{TEMPORARY}).
-@node NUMERIC, PRINT FORMATS, MODIFY VARS, Variable Attributes
+@node NUMERIC
@section NUMERIC
@vindex NUMERIC
Variables created with @cmd{NUMERIC} are initialized to the
system-missing value.
-@node PRINT FORMATS, RENAME VARIABLES, NUMERIC, Variable Attributes
+@node PRINT FORMATS
@section PRINT FORMATS
@vindex PRINT FORMATS
Its syntax is identical to that of @cmd{FORMATS} (@pxref{FORMATS}),
but @cmd{PRINT FORMATS} sets only print formats, not write formats.
-@node RENAME VARIABLES, VALUE LABELS, PRINT FORMATS, Variable Attributes
+@node RENAME VARIABLES
@section RENAME VARIABLES
@vindex RENAME VARIABLES
@cmd{RENAME VARIABLES} may not be specified following @cmd{TEMPORARY}
(@pxref{TEMPORARY}).
-@node VALUE LABELS, STRING, RENAME VARIABLES, Variable Attributes
+@node VALUE LABELS
@section VALUE LABELS
@vindex VALUE LABELS
(@pxref{ADD VALUE LABELS}) to add value labels without clearing those
already present.
-@node STRING, VARIABLE LABELS, VALUE LABELS, Variable Attributes
+@node STRING
@section STRING
@vindex STRING
Created variables are initialized to spaces.
-@node VARIABLE LABELS, VARIABLE ALIGNMENT, STRING, Variable Attributes
+@node VARIABLE LABELS
@section VARIABLE LABELS
@vindex VARIABLE LABELS
preceed the subsequent variable list with a slash (@samp{/}).
-@node VARIABLE ALIGNMENT, VARIABLE WIDTH, VARIABLE LABELS, Variable Attributes
+@node VARIABLE ALIGNMENT
@comment node-name, next, previous, u
@section VARIABLE ALIGNMENT
@vindex VARIABLE ALIGNMENT
-@node VARIABLE WIDTH, VARIABLE LEVEL, VARIABLE ALIGNMENT, Variable Attributes
+@node VARIABLE WIDTH
@comment node-name, next, previous, up
@section VARIABLE WIDTH
@vindex VARIABLE WIDTH
the display of variables in the PSPP output.
-@node VARIABLE LEVEL, VECTOR, VARIABLE WIDTH, Variable Attributes
+@node VARIABLE LEVEL
@comment node-name, next, previous, up
@section VARIABLE LEVEL
@vindex VARIABLE LEVEL
Currently, this has no effect except for certain third party software.
-@node VECTOR, WRITE FORMATS, VARIABLE LEVEL, Variable Attributes
+@node VECTOR
@section VECTOR
@vindex VECTOR
Variables within a vector may be referenced in expressions using
@code{vector(index)} syntax.
-@node WRITE FORMATS, , VECTOR, Variable Attributes
+@node WRITE FORMATS
@section WRITE FORMATS
@vindex WRITE FORMATS
projects / pspp-builds.git / commitdiff