2.1 Command-line processing

The thud command-line is thud followed by zero or more options followed by zero or more filenames.

     $ thud [options ...] [file1.th file2.th ...]

Here is a table of the command-line options that thud accepts. All options can be recognized by their short (single-hyphen) and long (double-hyphen) forms.

--version

Display THUD version and exit successfully.

--help

Display these options and exit successfully.

-s

--silent

Silent. THUD will be minimally verbose.

-d

--debug

Enable debugging support. This is recommended only for developers. Another way of enabling debugging output is to set the THUD_DEBUG environment variable. See -i dbglvls below.

-b

--batch

Batch mode. THUD will exit after processing the user initialization file. If -b is not specified, an interactive session begins. See --init below.

-F FACE

--face FACE

When used interactively, select THUD's face. A face is a mode of operation. thud has the following faces: full (thin layer over Guile), terse-cmd (terse command syntax for non-hacker users), and emacs (for emacs to talk to – still experimental).

See Faces, for more info.

-x FILE

--init FILE

Use file as initialization file instead of the default, which is the file .thud in your home directory. To use no file, try -x /dev/null. Only one -x option can be used on the command line.

-o FILE

--out FILE

Add the .th files (see below), do a compile-to file, then exit. See Data procedures.

-i ITEM

--info ITEM

Show information on item. The information is printed to standard output after which thud exits successfully. These items are recognized: help, warranty, version and dbglvls. (Specifying help lists all possible items.)

Command-line arguments following the options indicate files to be added to the workspace in the order given. These typically have the filename extension .th, although that is not required. As a heuristic, THUD does a link immediately after adding all the specified files.

See Boot sequence, for more info.