7 There are two separate user interfaces for PSPP.
8 There is the command line interface, which responds to commands
10 The command line interface is generally available on more platforms
11 than the graphic user interface and since it doesn't require a
12 graphics device it can be used from a remote terminal.
13 Platforms which have a windowing system may also be able to support
14 the graphic user interface.
15 The graphic user interface can perform all functionality of the
16 command line interface.
17 In addition it gives an instantaneous view of the data, variables and
20 Whichever interface you choose, a basic understanding of the concepts
21 used by PSPP is necessary before effective use of the system can be achieved.
25 * The command line user interface::
26 * The graphic user interface::
30 @node The command line user interface
31 @section The command line user interface
33 @cindex command line, options
34 @cindex options, command-line
37 pspp [ -B @var{dir} | --config-dir=@var{dir} ] [ -o @var{device} | --device=@var{device} ]
38 [ -a @{compatible|enhanced@} | --algorithm=@{compatible|enhanced@}]
39 [ -x @{compatible|enhanced@} | --syntax=@{compatible|enhanced@}]
40 [ -I- | --no-include ]
41 [ -I @var{dir} | --include=@var{dir} ] [ -i | --interactive ]
42 [ -r | --no-statrc ] [ -h | --help ] [ -l | --list ]
44 [ --testing-mode ] [ -V | --version ] [ -v | --verbose ]
45 [ @var{key}=@var{value} ] @var{file}@enddots{}
49 * Non-option Arguments:: Specifying syntax files and output devices.
50 * Configuration Options:: Change the configuration for the current run.
51 * Input and output options:: Controlling input and output files.
52 * Language control options:: Language variants.
53 * Informational options:: Helpful information about PSPP.
56 @node Non-option Arguments
57 @subsection Non-option Arguments
59 Syntax files and output device substitutions can be specified on
65 A file by itself on the command line will be executed as a syntax file.
66 If multiple files are specified, they are executed in order, as if
67 their contents had been given in a single file.
68 PSPP terminates after the syntax files run, unless the @code{-i} or
69 @code{--interactive} option is given (@pxref{Language control options}).
71 @item @var{key}=@var{value}
73 Defines an output device macro @var{key} to expand to @var{value},
74 overriding any macro having the same @var{key} defined in the device
75 configuration file. @xref{Macro definitions}.
79 There is one other way to specify a syntax file, if your operating
80 system supports it. If you have a syntax file @file{foobar.stat}, put
84 #! /usr/local/bin/pspp
87 at the top, and mark the file as executable with @code{chmod +x
88 foobar.stat}. (If PSPP is not installed in @file{/usr/local/bin},
89 then insert its actual installation directory into the syntax file
90 instead.) Now you should be able to invoke the syntax file just by
91 typing its name. You can include any options on the command line as
92 usual. PSPP entirely ignores any lines beginning with @samp{#!}.
94 @node Configuration Options
95 @subsection Configuration Options
97 Configuration options are used to change PSPP's configuration for the
98 current run. The configuration options are:
101 @item -a @{compatible|enhanced@}
102 @itemx --algorithm=@{compatible|enhanced@}
104 If you chose @code{compatible}, then PSPP will use the same algorithms
105 as used by some proprietary statistical analysis packages.
106 This is not recommended, as these algorithms are inferior and in some cases
108 The default setting is @code{enhanced}.
109 Certain commands have subcommands which allow you to override this setting on
113 @itemx --config-dir=@var{dir}
115 Sets the configuration directory to @var{dir}. @xref{File locations}.
117 @item -o @var{device}
118 @itemx --device=@var{device}
120 Selects the output device with name @var{device}. If this option is
121 given more than once, then all devices mentioned are selected. This
122 option disables all devices besides those mentioned on the command line.
125 @node Input and output options
126 @subsection Input and output options
128 Input and output options affect how PSPP reads input and writes
129 output. These are the input and output options:
135 Clears all directories from the include path. This includes all
136 directories put in the include path by default. @xref{Miscellaneous
140 @itemx --include=@var{dir}
142 Appends directory @var{dir} to the path that is searched for include
143 files in PSPP syntax files.
147 Invoke heuristics to assist with testing PSPP. For use by @code{make
148 check} and similar scripts.
151 @node Language control options
152 @subsection Language control options
154 Language control options control how PSPP syntax files are parsed and
155 interpreted. The available language control options are:
161 When a syntax file is specified on the command line, PSPP normally
162 terminates after processing it. Giving this option will cause PSPP to
163 bring up a command prompt after processing the syntax file.
165 In addition, this forces syntax files to be interpreted in interactive
166 mode, rather than the default batch mode. @xref{Tokenizing lines}, for
167 information on the differences between batch mode and interactive mode
168 command interpretation.
173 Prevents the execution of the PSPP startup syntax file.
178 Disables certain unsafe operations. This includes the ERASE and
179 HOST commands, as well as use of pipes as input and output files.
182 @node Informational options
183 @subsection Informational options
185 Informational options cause information about PSPP to be written to
186 the terminal. Here are the available options:
192 Prints a message describing PSPP command-line syntax and the available
193 device driver classes, then terminates.
198 Lists the available device driver classes, then terminates.
200 @item -x @{compatible|enhanced@}
201 @itemx --syntax=@{compatible|enhanced@}
203 If you chose @code{compatible}, then PSPP will only accept command syntax that
204 is compatible with the proprietary program SPSS.
205 If you choose @code{enhanced} then additional syntax will be available.
206 The default is @code{enhanced}.
212 Prints a brief message listing PSPP's version, warranties you don't
213 have, copying conditions and copyright, and e-mail address for bug
214 reports, then terminates.
219 Increments PSPP's verbosity level. Higher verbosity levels cause
220 PSPP to display greater amounts of information about what it is
221 doing. Often useful for debugging PSPP's configuration.
223 This option can be given multiple times to set the verbosity level to
224 that value. The default verbosity level is 0, in which no informational
225 messages will be displayed.
227 Higher verbosity levels cause messages to be displayed when the
228 corresponding events take place.
233 Driver and subsystem initializations.
237 Completion of driver initializations. Beginning of driver closings.
241 Completion of driver closings.
245 Files searched for; success of searches.
249 Individual directories included in file searches.
252 Each verbosity level also includes messages from lower verbosity levels.
257 @node The graphic user interface
258 @section The graphic user interface
260 @cindex Graphic user interface
263 The graphic user interface can be started by typing @command{psppire} at a
265 Alternatively many systems have a system of interactive menus or buttons
266 from which @command{psppire} can be started by a series of mouse clicks.
268 Once the principles of the PSPP system are understood,
269 the graphic user interface is designed to be largely intuitive, and
270 for this reason is covered only very briefly by this manual.