sd: Scripts Dir

A tool to keep utility scripts neatly organized.

Overview
Installing
Running
Contributing
Thanks

Overview

sd scans and provides completion for a nested tree of executable script files. For example, if you want to be able to run:

sd foo bar 123

All you need to do is create the following structure:

~/.sd/
  |- foo/
  |  |- README
     |- bar

The first line of README is a short description of foo. Like this:

$ sd --help
Usage:
  sd [command]

Available Commands:
  foo         Commands related to foo

The rest of the README file gets displayed when the user asks for further help:

$ sd foo --help
Commands related to foo

This is the longer text description of all the subcommands, switches
and examples of foo. It is displayed when `sd foo --help` is called.

Usage:
...

The bar script must be marked executable (chmod +x). Any files not marked executable will be ignored. The help text for it looks like this:

$ sd foo bar --help
Bars the foos.

Usage:
  sd foo bar [flags]

Examples:
  sd foo bar 123

In order to document the script, sd pays attention to a few special comments:

#!/bin/sh
#
# bar: Bars the foos.
# usage: bar foo [quux]
# example: bar 12 23
#
echo "sd foo bar has been called"

More will be added in the future, so you'll be able to specify and document flags, environment variables, and so on.

Installing

Homebrew

The easiest way to install and keep sd up-to-date for MacOS users is through Homebrew. First, add the cv/taps tap to your Homebrew install:

$ brew tap cv/taps git@github.com:cv/taps.git
==> Tapping cv/taps
Cloning into '/usr/local/Homebrew/Library/Taps/cv/homebrew-taps'...
remote: Counting objects: 5, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 5 (delta 0), reused 0 (delta 0), pack-reused 0
Receiving objects: 100% (5/5), done.
Tapped 1 formula (27 files, 23KB)

Then install sd with brew install sd:

$ brew install sd
==> Installing sd from cv/taps
==> Downloading https://github.com/cv/sd/releases/download/v0.1.1/sd_0.1.1_Darwin_x86_64.tar.gz
==> Downloading from https://github-production-release-asset-2e65be.s3.amazonaws.com/128149837/9149f9cc-39b3-11e8-98d8-b5bf16da23b7?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2
######################################################################## 100.0%
🍺  /usr/local/Cellar/sd/0.1.1: 5 files, 3MB, built in 7 seconds

Go

If you have a Go development environment installed, go get should work as expected:

$ go get -u github.com/cv/sd

Other distributions

Alternatively, you can grab one of the packages from the Releases tab.

Running

Flags

sd pays attention to the following flags in any command:

-d or --debug: Turn on debugging. Especially useful if you are trying to figure out why any given script isn't loading, or isn't loading quite like you'd want it.
-e or --edit: Instead of executing a script, sd will open it in your favorite editor, as defined by the VISUAL or EDITOR environment variables.
-h or --help: Shows help text for anything.
--version: Displays the version information and exits.

Aliasing

The hidden --alias=STRING flag tells sd to behave as if it were called STRING. This is useful when aliasing sd to something else more memorable, or to scope it to the specific usage of a project.

For example, if you call it with sd --alias foo, it will show the following usage:

Usage:
  foo [flags]
  foo [command]

Available Commands:
...

Use "foo [command] --help" for more information about a command.

Completions

To enable shell completions, making sd much more pleasant to use, run:

$ source <(sd completions bash)

Or add it to /etc/bash-completion.d, as documented in this guide.

Mixing aliasing and completions can be very useful in creating a CLI experience that provides inline documentation, good completion and a familiar, integrated, look-and-feel.

Multiple sources

sd loads scripts and dirs in the following order:

Your $HOME/.sd directory
Script directories listed in SD_PATH
The scripts directory under the current location

Contributing

Yes, please! Check out the issues and pull requests. Any feedback is greatly appreciated!

Thanks

Steve Francia et al for Cobra
Fabio Rehm for lots of feedback and ideas

cv / sd

readme