System level commands

These commands control system level activities. Unlike all the above commands they are not followed by a period.

pwd

Prints the path of the working directory.

ls $\lbrace$flags$\rbrace$ $\lbrace$directories$\rbrace$

Runs the UNIX ls command to list the files in the specified directories or working directory if none specified. The allowable flags depend on your local implementation of ls. Example:

  ls -lF /usr/bin/usr/local

cd directory-name

Changes the working directory to directory-name.

pushd directory-name

Saves the current working directory on a stack and then changes the working directory to directory-name.

popd

Changes the working directory to that which is on the top of the directory stack and pops the directory stack.

in file-name

Causes a specified file to be included at this point. For files specified by a bare file name, it checks (with .maude, .fm, .obj extensions) if the filename is in one of these locations: (a) the current directory; (b) the directories in the MAUDE_LIB environment variable, and (c) the directory containing the executable. Otherwise, the full file name must be given, together with a full path name if the file is not in the current working directory. The in command may be nested, i.e., the included file may contain in commands. Example:

  in ../Examples/foo.maude

Notice that compilation of operator declarations and statements is done lazily, so that the module is not necessarily fully compiled when included. This implies that some warnings and advisories will only show up when a reduction actually takes place in the module. This also holds for a module that is entered by writing it in the prompt instead of a file.

load file-name

Performs the same job as in but does not produce detailed output as modules are entered. Example:

  load ../Examples/foo.maude

eof

Causes the interpreter to respond as if it had reached the end of file.

quit

Causes the interpreter to exit.