Here we describe Guile's command-line processing in detail. Guile processes its arguments from left to right, recognizing the switches described below. For examples, see section Scripting Examples.
-s script arg...
load
function would. After loading script, exit. Any
command-line arguments arg... following script become the
script's arguments; the command-line
function returns a list of
strings of the form (script arg...)
.
-c expr arg...
command-line
function returns a list of strings of the form
(guile arg...)
, where guile is the path of the
Guile executable.
-- arg...
--
become command-line arguments for the interactive session; the
command-line
function returns a list of strings of the form
(guile arg...)
, where guile is the path of the
Guile executable.
-l file
-e function
-s
) or evaluating the expression (with
-c
), apply function to a list containing the program name
and the command-line arguments -- the list provided by the
command-line
function.
A -e
switch can appear anywhere in the argument list, but Guile
always invokes the function as the last action it performs.
This is weird, but because of the way script invocation works under
POSIX, the -s
option must always come last in the list.
See section Scripting Examples.
-ds
-s
option as if it occurred at this point in the
command line; load the script here.
This switch is necessary because, although the POSIX script invocation
mechanism effectively requires the -s
option to appear last, the
programmer may well want to run the script before other actions
requested on the command line. For examples, see section Scripting Examples.
\
--emacs
#t
.
This switch is still experimental.
-h, --help
-v, --version
Go to the first, previous, next, last section, table of contents.