Command
This is to do with command line handling. The Cabal command line is
organised into a number of named sub-commands (much like darcs). The
CommandUI abstraction represents one of these sub-commands,
with a name, description, a set of flags. Commands can be associated
with actions and run. It handles some common stuff automatically, like
the
--help and command line completion flags. It is designed
to allow other tools make derived commands. This feature is used
heavily in
cabal-install.
The specification for the expected behaviour of an
Action.
These are used to generate sequences of actions to test.
This is the main type you will use when writing state machine tests.
gen is usually an instance of
MonadGen, and
m
is usually an instance of
MonadTest. These constraints appear
when you pass your
Command list to
sequential or
parallel.
The commands suported by the view controller.
This module provides functions for calling command line programs,
primarily
command and
cmd. As a simple example:
command [] "gcc" ["-c",myfile]
The functions from this module are now available directly from
Development.Shake. You should only need to import this module
if you are using the
cmd function in the
IO monad.
Represents a reference to a command. Provides a title which will be
used to represent a command in the UI and, optionally, an array of
arguments which will be passed to the command handler function when
invoked.
SMTP commands.
Supports basic and extended SMTP protocol without TLS support.
For each command we provide list of the expected reply codes that
happens in success and failure cases respectively.
Might also be the Windows key or the Super key
Exported Command. Callable via
:Name arg1 arg2.
- Name of the command (must start with an uppercase letter)
- Options to configure neovim's behavior for calling the
command
Implementation of the 'cabal init' command, which creates an initial
.cabal file for a project.
Previously symbolically executed command
Invariant: the variables must be the variables in the response.