This type is a simple wrapper for a type Shelly.Sh. Sh contains a list of results.

Performs shelly and then an empty action return ().

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.

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).

Performs shellyNoDir and then an empty action return ().

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. Also commands are not printed. See sub.

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

Create a sub-Sh with shell character escaping on or off

Create a sub-Sh with stdout printing on or off

Create a sub-Sh with command echoing on or off

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.

Pack list of results. It performs concat inside Sh.

Unpack list of results.

Transform result as list. It can be useful for filtering.

Execute an external command. Takes the command name (no shell allowed, just a name of something that can be found via PATH; FIXME: setenv'd PATH is not taken into account when finding the exe name)

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 but still consume the result by using run_, If you want to avoid the memory and need to process the output then use runFoldLines.

The same as run, but return () instead of the stdout content.

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. 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. a FilePath is converted to Text with toTextIgnore. You will need to add the following to your module:

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

Pipe operator. set the stdout the first command as the stdin of the second.

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]

bind some arguments to run_ for re-use Example: monit_ = command_ monit [-c, monitrc]

bind some arguments to run for re-use, and expect 1 argument Example: git = command1 git []; git pull [origin, master]

bind some arguments to run for re-use, and expect 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: the commands will not be shell escaped. Internally the list of commands are combined with the string && before given to ssh.

same as sshPairs, but returns ()

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.

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

add the filepath onto the PATH env variable FIXME: only effects the PATH once the process is ran, as per comments in which

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. This may have performance repercussions if you are doing hundreds of thousands of filesystem operations. You will want to handle these issues differently in those cases.

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

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 occured. 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?

Get a full path to an executable on PATH, if exists. FIXME does not respect setenv'd environment and uses findExecutable which uses the PATH inherited from the process environment. FIXME: findExecutable does not maintain a hash of existing commands and does a ton of file stats

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

uses System.FilePath.CurrentOS, but can automatically convert a Text

uses System.FilePath.CurrentOS, but can automatically convert a Text

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

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

flipped hasExtension for Text

Currently a renameFile wrapper. TODO: Support cross-filesystem move. TODO: Support directory paths in the second parameter, like in cp.

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 removeTree

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.

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 (# []) 

(Strictly) read file into a Text. All other functions use Lazy Text. So Internally this reads a file as strict text and then converts it to lazy text, which is inefficient

wraps ByteSting readFile

Write a Lazy Text to a file.

Append a Lazy 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.

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) -> ...).

Catch an exception in the Sh monad.

Catch an exception in the Sh monad.

You need this when using catches_sh.

Catch multiple exceptions in the Sh monad.

Catch an exception in the Sh monad.

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

An infix synonym for fmap.

A monadic-conditional version of the when guard.

A monadic-conditional version of the unless guard.

Run a Sh computation and collect timing information.

Lift a computation from the IO monad.

Conditional execution of monadic expressions. For example,

       when debug (putStr "Debugging\n")

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

The reverse of when.

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