TTY::Command Gitter

Gem Version Build Status Build status Code Climate Coverage Status Inline docs

Run external commands with pretty output logging and capture stdout, stderr and exit status. Redirect stdin, stdout and stderr of each command to a file or a string.

TTY::Command provides independent command execution component for TTY toolkit.


Complex software projects aren't just a single app. These projects usually spawn dozens or hundreds of supplementary standalone scripts which are just as important as the app itself. Examples include - data validation, deployment, monitoring, database maintenance, backup & restore, configuration management, crawling, ETL, analytics, log file processing, custom reports, etc. One of the contributors to TTY::Command counted 222 scripts in the bin directory for his startup.

Why should we be handcuffed to sh or bash for these scripts when we could be using Ruby? Ruby is easier to write and more fun, and we gain a lot by using a better language. It's nice for everyone to just use Ruby everywhere.

TTY::Command tries to add value in other ways. It'll halt automatically if a command fails. It's easy to get verbose or quiet output as appropriate, or even capture output and parse it with Ruby. Escaping arguments is a breeze. These are all areas where traditional shell scripts tend to fall flat.


Add this line to your application's Gemfile:

gem 'tty-command'

And then execute:

$ bundle

Or install it yourself as:

$ gem install tty-command


1. Usage

Create a command instance and then run some commands:

cmd ='ls -la')'echo Hello!')

Note that run will throw an exception if the command fails. This is already an improvement over ordinary shell scripts, which just keep on going when things go bad. That usually makes things worse.

You can use the return value to capture stdout and stderr:

out, err ='cat ~/.bashrc | grep alias')

Instead of using a plain old string, you can break up the arguments and they'll get escaped if necessary:

path = "hello world"
FileUtils.touch(path)"sum #{path}")  # this will fail due to bad escaping"sum", path)    # this gets escaped automatically

2. Interface

2.1 Run

Run starts the specified command and waits for it to complete.

The argument signature of run is as follows:

run([env], command, [argv1, ...], [options])

The env, command and options arguments are described in the following sections.

For example, to display file contents:'cat file.txt')

If the command succeeds, a TTY::Command::Result is returned that records stdout and stderr:

out, err ='date')
puts "The date is #{out}"
# => "The date is Tue 10 May 2016 22:30:15 BST\n"

You can also pass a block that gets invoked anytime stdout and/or stderr receive output:'long running script') do |out, err|
  output << out if out
  errors << err if err

If the command fails (with a non-zero exit code), a TTY::Command::ExitError is raised. The ExitError message will include:

  • the name of command executed
  • the exit status
  • stdout bytes
  • stderr bytes

If the error output is very long, the stderr may contain only a prefix, number of omitted bytes and suffix.

2.2 Run!

If you expect a command to fail occasionally, use run! instead. Then you can detect failures and respond appropriately. For example:

if!('which xyzzy').failure?'brew install xyzzy')

2.3 Logging

By default, when a command is run, the command and the output are printed to stdout using the :pretty printer. If you wish to change printer you can do so by passing a :printer option:

  • :null - no output
  • :pretty - colorful output
  • :progress - minimal output with green dot for success and F for failure
  • :quiet - only output actual command stdout and stderr

like so:

cmd = :progress)

By default the printers log to stdout but this can be changed by passing an object that responds to << message:

logger ='dev.log')
cmd = logger)

You can force the printer to always in print in color by passing the :color option:

cmd = true)

2.3.1 Color

When using printers you can switch off coloring by using color option set to false.

2.3.2 Uuid

By default when logging is enabled each log entry is prefixed by specific command run uuid number. This number can be switched off using uuid option:

cmd = uuid: false'rm -R all_my_files')
# => rm -r all_my_files

2.4 Dry run

Sometimes it can be useful to put your script into a "dry run" mode that prints commands without actually running them. To simulate execution of the command use the :dry_run option:

cmd = true), 'all_my_files')
# => [123abc] (dry run) rm all_my_files

To check what mode the command is in use the dry_run? query helper:

cmd.dry_run? # => true

2.5 Wait

If you need to wait for a long running script and stop it when a given pattern has been matched use wait like so:

cmd.wait 'tail -f /var/log/production.log', /something happened/

2.6 Test

To simulate classic bash test command you case use test method with expression to check as a first argument:

if cmd.test '-e /etc/passwd'
  puts "Sweet..."
  puts "Ohh no! Where is it?"
  exit 1

2.7 Ruby interpreter

In order to run a command with Ruby interpreter do:

cmd.ruby %q{-e "puts 'Hello world'"}

3. Advanced Interface

3.1 Environment variables

The environment variables need to be provided as hash entries, that can be set directly as a first argument:{'RAILS_ENV' => 'PRODUCTION'}, :rails, 'server')

or as an option with :env key:, 'server', env: {rails_env: :production})

When a value in env is nil, the variable is unset in the child process:, 'hello', env: {foo: 'bar', baz: nil})

3.2 Options

When a hash is given in the last argument (options), it allows to specify a current directory, umask, user, group and and zero or more fd redirects for the child process.

3.2.1 Redirection

There are few ways you can redirect commands output.

You can directly use shell redirection like so:

out, err ="ls 1&>2")
puts err
# =>
# Gemfile
# ...

You can provide redirection as additional hash options where the key is one of :in, :out, :err, an integer (a file descriptor for the child process), an IO or array. For example, stderr can be merged into stdout as follows:, :err => :out), :stderr => :stdout), 2 => 1), STDERR => :out), STDERR => STDOUT)

The hash key and value specify a file descriptor in the child process (stderr & stdout in the examples).

You can also redirect to a file:, :in => 'file'), :in => open('/etc/passwd')), :out => 'log'), :out => "/dev/null"), :out => 'out.log', :err => "err.log"), [:out, :err] => "log")"ls 1>&2", :err => 'log')

It is possible to specify flags and permissions of file creation explicitly by passing an array value:, :out => ['log', 'w']) # 0664 assumed, :out => ['log', 'w', 0600]), :out => ['log', File::WRONLY|File::EXCL|File::CREAT, 0600])

You can, for example, read data from one source and output to another:"cat", :in => "Gemfile", :out => 'gemfile.log')

3.2.2 Handling Input

You can provide input to stdin stream using the :input key. For instance, given the following executable called cli that expects name from stdin:

name = $stdin.gets
puts "Your name: #{name}"

In order to execute cli with name input do:'cli', input: "Piotr\n")
# => Your name: Piotr

Alternatively, you can pass input via the :in option, by passing a StringIO Object. This object might have more than one line, if the executed command reads more than once from STDIN.

Assume you have run a program, that first asks for your email address and then for a password:

in_stream =
in_stream.puts ""
in_stream.puts "password"
in_stream.rewind"my_cli_program", "login", in: in_stream).out

3.2.3 Timeout

You can timeout command execuation by providing the :timeout option in seconds:"while test 1; sleep 1; done", timeout: 5)

And to set it for all commands do:

cmd = 5)

Please run examples/timeout.rb to see timeout in action.

3.2.4 Binary mode

By default the standard input, output and error are non-binary. However, you can change to read and write in binary mode by using the :binmode option like so:"echo 'hello'", binmode: true)

To set all commands to be run in binary mode do:

cmd = true)

3.2.5 Signal

You can specify process termination signal other than the defaut SIGTERM:"whilte test1; sleep1; done", timeout: 5, signal: :KILL)

3.2.6 PTY(pseudo terminal)

The :pty configuration option causes the command to be executed in subprocess where each stream is a pseudo terminal. By default this options is set to false. However, some comamnds may require a terminal like device to work correctly. For example, a command may emit colored output only if it is running via terminal.

In order to run command in pseudo terminal, either set the flag globally for all commands:

cmd = true)

or for each executed command individually:"echo 'hello'", pty: true)

Please note though, that setting :pty to true may change how the command behaves. For instance, on unix like systems the line feed character \n in output will be prefixed with carriage return \r:

out, _ ="echo 'hello'")
out # => "hello\n"

and with :pty option:

out, _ ="echo 'hello'", pty: true)
out # => "hello\r\n"

In addition, any input to command may be echoed to the standard output.

3.2.7 Current directory

To change directory in which the command is run pass the :chdir option:, 'hello', chdir: '/var/tmp')

3.2.8 User

To run command as a given user do:, 'hello', user: 'piotr')

3.2.9 Group

To run command as part of group do:, 'hello', group: 'devs')

3.2.10 Umask

To run command with umask do:, 'hello', umask: '007')

3.3 Result

Each time you run command the stdout and stderr are captured and return as result. The result can be examined directly by casting it to tuple:

out, err =, 'Hello')

However, if you want to you can defer reading:

result =, 'Hello')

3.3.1 success?

To check if command exited successfully use success?:

result =, 'Hello')
result.success? # => true

3.3.2 failure?

To check if command exited unsuccessfully use failure? or failed?:

result =, 'Hello')
result.failure?  # => false
result.failed?   # => false

3.3.3 exited?

To check if command ran to completion use exited? or complete?:

result =, 'Hello')
result.exited?    # => true
result.complete?  # => true

3.3.4 each

The result itself is an enumerable and allows you to iterate over the stdout output:

result =, '-1')
result.each { |line| puts line }
# =>
#  Gemfile
#  Gemfile.lock
#  ...
#  lib
#  pkg
#  spec
#  tasks

By default the linefeed character \n is used as a delimiter but this can be changed either globally by calling record_separator:

TTY::Command.record_separator = "\n\r"

or configured per each call by passing delimiter as an argument:, '-1').each("\t") { ... }

3.4 Custom printer

If the built-in printers do not meet your requirements you can create your own. At the very minimum you need to specify the write method that will be called during the lifecycle of command execution:

CustomPrinter < TTY::Command::Printers::Abstract
  def write(message)
    puts message

printer = CustomPrinter

cmd = printer)

4. Example

Here's a slightly more elaborate example to illustrate how tty-command can improve on plain old shell scripts. This example installs a new version of Ruby on an Ubuntu machine.

cmd =

# dependencies "apt-get -y install build-essential checkinstall"

# fetch ruby if necessary
if !File.exists?("ruby-2.3.0.tar.gz")
  puts "Downloading..." "wget" "tar xvzf ruby-2.3.0.tar.gz"

# now install
Dir.chdir("ruby-2.3.0") do
  puts "Building..." "./configure --prefix=/usr/local" "make"


After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.


Bug reports and pull requests are welcome on GitHub at This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.


The gem is available as open source under the terms of the MIT License.


Copyright (c) 2016-2017 Piotr Murach. See LICENSE for further details.