ShIO is Deprecated in favor of Sh, which is easier to type.

Enter a Sh from (Monad)IO. The environment and working directories are inherited from the current process-wide values. Any subsequent changes in processwide working directory or environment are not reflected in the running Sh.

Deprecated now, just use shelly, whose default has been changed. Using this entry point does not create a .shelly directory in the case of failure. Instead it logs directly into the standard error stream (stderr).

Using this entry point creates a .shelly directory in the case of failure where errors are recorded.

spawn an asynchronous action with a copy of the current state

Enter a sub-Sh that inherits the environment The original state will be restored when the sub-Sh completes. Exceptions are propagated normally.

Create a sub-Sh in which external command outputs are not echoed and commands are not printed. See sub.

Create a sub-Sh in which external command outputs are echoed and Executed commands are printed See sub.

Create a sub-Sh with shell character escaping on or off. Defaults to True.

Setting to False allows for shell wildcard such as * to be expanded by the shell along with any other special shell characters. As a side-effect, setting to False causes changes to PATH to be ignored: see the run documentation.

Create a sub-Sh with stdout printing on or off Defaults to True.

Create a sub-Sh with stderr printing on or off Defaults to True.

Create a sub-Sh with command echoing on or off Defaults to False, set to True by verbosely

When running an external command, apply the given initializers to the specified handles for that command. This can for example be used to change the encoding of the handles or set them into binary mode.

Create a sub-Sh where commands are not traced Defaults to True. You should only set to False temporarily for very specific reasons

named after bash -e errexit. Defaults to True. When True, throw an exception on a non-zero exit code. When False, ignore a non-zero exit code. Not recommended to set to False unless you are specifically checking the error code with lastExitCode.

Create a sub-Sh in which stdout is sent to the user-defined logger. When running with silently the given log will not be called for any output. Likewise the log will also not be called for output from run_ and bash_ commands.

Create a sub-Sh in which stderr is sent to the user-defined logger. When running with silently the given log will not be called for any output. However, unlike log_stdout_with the log will be called for output from run_ and bash_ commands.

Execute an external command. Takes the command name and arguments.

You may prefer using cmd instead, which is a variadic argument version of this function.

stdout and stderr are collected. The stdout is returned as a result of run, and complete stderr output is available after the fact using lastStderr

All of the stdout output will be loaded into memory. You can avoid this if you don't need stdout by using run_, If you want to avoid the memory and need to process the output then use runFoldLines or runHandle or runHandles.

By default shell characters are escaped and the command name is a name of a program that can be found via PATH. Shelly will look through the PATH itself to find the command.

When escaping is set to False, shell characters are allowed. Since there is no longer a guarantee that a single program name is given, Shelly cannot look in the PATH for it. a PATH modified by setenv is not taken into account when finding the exe name. Instead the original Haskell program PATH is used. On a Posix system the env command can be used to make the setenv PATH used when escaping is set to False. env echo hello instead of echo hello

the same as run, but return () instead of the stdout content stdout will be read and discarded line-by-line

used by run. fold over stdout line-by-line as it is read to avoid keeping it in memory stderr is still being placed in memory under the assumption it is always relatively small

variadic argument version of run. Please see the documenation for run.

The syntax is more convenient, but more importantly it also allows the use of a FilePath as a command argument. So an argument can be a Text or a FilePath without manual conversions. a FilePath is automatically converted to Text with toTextIgnore.

Convenient usage of cmd requires the following:

{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE ExtendedDefaultRules #-}
{-# OPTIONS_GHC -fno-warn-type-defaults #-}
import Shelly
import qualified Data.Text as T
default (T.Text)

Like run, but it invokes the user-requested program with _bash_.

Use this with bash to set _pipefail_

bashPipeFail $ bash "echo foo | echo"

Pipe operator. set the stdout the first command as the stdin of the second. This does not create a shell-level pipe, but hopefully it will in the future. To create a shell level pipe you can set escaping False and use a pipe | character in a command.

The output of last external command. See run.

set the stdin to be used and cleared by the next run.

The exit code from the last command. Unless you set errExit to False you won't get a chance to use this: a non-zero exit code will throw an exception.

bind some arguments to run for re-use. Example:

monit = command "monit" ["-c", "monitrc"]
monit ["stop", "program"]

bind some arguments to run_ for re-use. Example:

monit_ = command_ "monit" ["-c", "monitrc"]
monit_ ["stop", "program"]

bind some arguments to run for re-use, and require 1 argument. Example:

git = command1 "git" []
git "pull" ["origin", "master"]

bind some arguments to run_ for re-use, and require 1 argument. Example:

git_ = command1_ "git" []
git "pull" ["origin", "master"]

run commands over SSH. An ssh executable is expected in your path. Commands are in the same form as run, but given as pairs

sshPairs "server-name" [("cd", "dir"), ("rm",["-r","dir2"])]

This interface is crude, but it works for now.

Please note this sets escaping to False, and the remote commands are quoted with single quotes, in a way such that the remote commands will see the literal values you passed, this means that no variable expansion and alike will done on either the local shell or the remote shell, and that if there are a single or double quotes in your arguments, they need not to be quoted manually.

Internally the list of commands are combined with the string && before given to ssh.

Same as sshPairs, but combines commands with the string &, so they will be started in parallell.

same as sshPairs, but returns ()

same as sshPairsP, but returns ()

Like sshPairs, but allows for arguments to the call to ssh.

For the variadic function cmd

partially applied variadic functions require type signatures

Argument converter for the variadic argument version of run called cmd. Useful for a type signature of a function that uses cmd

Similar to run but gives the raw stdout handle in a callback. If you want even more control, use runHandles.

Similar to run but gives direct access to all input and output handles.

Be careful when using the optional input handles. If you specify Inherit for a handle then attempting to access the handle in your callback is an error

Transfer from one handle to another For example, send contents of a process output to stdout. does not close the write handle.

Also, return the complete contents being streamed line by line.

Transfer from one handle to another For example, send contents of a process output to stdout. does not close the write handle.

Also, fold over the contents being streamed line by line

Initialize a handle before using it

A collection of initializers for the three standard process handles

Apply a single initializer to the two output process handles (stdout and stderr)

Apply a single initializer to all three standard process handles (stdin, stdout and stderr)

Set an environment variable. The environment is maintained in Sh internally, and is passed to any external commands to be executed.

Fetch the current value of an environment variable. if non-existant or empty text, will be Nothing

Fetch the current value of an environment variable. Both empty and non-existent variables give empty string as a result.

deprecated

Fetch the current value of an environment variable. Both empty and non-existent variables give the default Text value as a result

get the full environment

add the filepath onto the PATH env variable

prepend the filepath to the PATH env variable similar to appendToPath but gives high priority to the filepath instead of low priority.

Change current working directory of Sh. This does *not* change the working directory of the process we are running it. Instead, Sh keeps track of its own working directory and builds absolute paths internally instead of passing down relative paths.

cd, execute a Sh action in the new directory and then pop back to the original directory

chdir, but first create the directory if it does not exit

Obtain the current (Sh) working directory.

Echo text to standard (error, when using _err variants) output. The _n variants do not print a final newline.

Echo text to standard (error, when using _err variants) output. The _n variants do not print a final newline.

Echo text to standard (error, when using _err variants) output. The _n variants do not print a final newline.

Echo text to standard (error, when using _err variants) output. The _n variants do not print a final newline.

a print lifted into Sh

a print lifted into Sh using stderr

same as trace, but use it combinator style

internally log what occurred. Log will be re-played on failure.

List directory contents. Does *not* include "." and "..", but it does include (other) hidden files.

Get back [Text] instead of [FilePath]

Does a path point to an existing filesystem object?

Does a path point to an existing file?

Does a path point to an existing directory?

Does a path point to a symlink?

Test that a file is in the PATH and also executable

Get a full path to an executable by looking at the PATH environement variable. Windows normally looks in additional places besides the PATH: this does not duplicate that behavior.

Make a relative path absolute by combining with the working directory. An absolute path is returned as is. To create a relative path, use relPath.

uses System.FilePath, but can automatically convert a Text

uses System.FilePath, but can automatically convert a Text

makes an absolute path. Like canonicalize, but on an exception returns absPath

Obtain a (reasonably) canonic file path to a filesystem object. Based on "canonicalizePath" in system-fileio.

Makes a relative path relative to the current Sh working directory. An absolute path is returned as is. To create an absolute path, use absPath

make the second path relative to the first Uses stripPrefix, but will canonicalize the paths if necessary

deprecated

flipped hasExtension for Text

Move a file. The second path could be a directory, in which case the original file is moved into that directory. wraps directory renameFile, which may not work across FS boundaries

Remove a file. Does fail if the file does not exist (use rm_f instead) or is not a file.

Remove a file. Does not fail if the file does not exist. Does fail if the file is not a file.

A swiss army cannon for removing things. Actually this goes farther than a normal rm -rf, as it will circumvent permission problems for the files we own. Use carefully. Uses removeDirectoryRecursive

Copy a file. The second path could be a directory, in which case the original file name is used, in that directory.

Copy a file, or a directory recursively. uses cp

Create a new directory (fails if the directory exists).

Create a new directory, including parents (succeeds if the directory already exists).

Create a new directory tree. You can describe a bunch of directories as a tree and this function will create all subdirectories. An example:

exec = mkTree $
          "package" # [
               "src" # [
                   "Data" # leaves ["Tree", "List", "Set", "Map"]
               ],
               "test" # leaves ["QuickCheck", "HUnit"],
               "dist/doc/html" # []
           ]
        where (#) = Node
              leaves = map (# [])

wraps ByteSting readFile

Write a Text to a file.

Append a Text to a file.

Update a file, creating (a blank file) if it does not exist.

Create a temporary directory and pass it as a parameter to a Sh computation. The directory is nuked afterwards.

exit 0 means no errors, all other codes are error conditions

echo a message and exit with status 1

for exiting with status > 0 without printing debug information

fail that takes a Text

A helper to catch any exception (same as ... catch (e :: SomeException) -> ...).

Same as a normal catch but specialized for the Sh monad.

Same as a normal handle but specialized for the Sh monad.

Handle any exception in the Sh monad.

Same as a normal finally but specialized for the Sh monad.

You need to wrap exception handlers with this when using catches_sh.

Same as a normal catches, but specialized for the Sh monad.

Catch any exception in the Sh monad.

Shelly's wrapper around exceptions thrown in its monad

silently uses the Right or Left value of "Filesystem.Path.CurrentOS.toText"

Convert Text to a FilePath-

A monadic-conditional version of the "when" guard.

A monadic-conditional version of the unless guard.

Run a Sh computation and collect timing information. The value returned is the amount of _real_ time spent running the computation in seconds, as measured by the system clock. The precision is determined by the resolution of getCurrentTime.

threadDelay wrapper that uses seconds

Lift a computation from the IO monad.

Conditional execution of Applicative expressions. For example,

when debug (putStrLn "Debugging")

will output the string Debugging if the Boolean value debug is True, and otherwise do nothing.

The reverse of when.

File and directory names are values of type String, whose precise meaning is operating system dependent. Files can be opened, yielding a handle which can then be used to operate on the contents of that file.

An infix synonym for fmap.

The name of this operator is an allusion to $. Note the similarities between their types:

 ($)  ::              (a -> b) ->   a ->   b
(<$>) :: Functor f => (a -> b) -> f a -> f b

Whereas $ is function application, <$> is function application lifted over a Functor.

Examples

>>> show <$> Nothing
Nothing
>>> show <$> Just 3
Just "3"

>>> show <$> Left 17
Left 17
>>> show <$> Right 17
Right "17"

>>> (*2) <$> [1,2,3]
[2,4,6]

>>> even <$> (2,2)
(2,True)

List directory recursively (like the POSIX utility "find"). listing is relative if the path given is relative. If you want to filter out some results or fold over them you can do that with the returned files. A more efficient approach is to use one of the other find functions.

find that filters the found files as it finds. Files must satisfy the given filter to be returned in the result.

Fold an arbitrary folding function over files froma a find. Like findWhen but use a more general fold rather than a filter.

find that filters out directories as it finds Filtering out directories can make a find much more efficient by avoiding entire trees of files.

similar findWhen, but also filter out directories Alternatively, similar to findDirFilter, but also filter out files Filtering out directories makes the find much more efficient

like findDirFilterWhen but use a folding function rather than a filter The most general finder: you likely want a more specific one

find-command follows symbolic links. Defaults to False. When True, follow symbolic links. When False, never follow symbolic links.