No description
Find a file
2018-12-26 15:34:14 -05:00
.circleci adjust ci caching 2018-12-23 00:11:52 -05:00
src Tweak flags and help output 2018-12-26 14:31:44 -05:00
.gitignore start 2018-12-23 00:01:35 -05:00
Cargo.lock (cargo-release) version 0.2.0 2018-12-26 15:34:14 -05:00
Cargo.toml (cargo-release) version 0.2.0 2018-12-26 15:34:14 -05:00
LICENSE Add license + CI 2018-12-23 00:04:55 -05:00
README.md Update README 2018-12-26 14:23:13 -05:00

sd - s[earch] & d[isplace]

sd is an intuitive find & replace CLI.

The Pitch

Why use it over any existing tools?

Painless regular expressions

sd uses regex syntax that you already know from JavaScript and Python. Forget about dealing with quirks of sed or awk - get productive immediately.

String-literal mode

Non-regex find & replace. No more backslashes or remembering which characters are special and need to be escaped.

Easy to read, easy to write

Find & replace expressions are split up, which makes them easy to read and write.

Comparison to sed

While sed does a whole lot more, sd focuses on doing just one thing and doing it well.

Some cherry-picked examples, where sd shines:

  • Replace newlines with commas:
    • sd: sd '\r' ','
    • sed: sed ':a;N;$!ba;s/\r/,/g'
  • Extracting stuff out of strings with special characters
    • sd: echo "{((sample with /path/))}" | sd '\{\(\(.*(/.*/)\)\)\}' '$1'
    • sed
      • incorrect, but closest I could get after 15 minutes of struggle
      • echo "{((sample with /path/))}" | sed 's/{((\.\*\(\/.*\/\)))}/\1/g'

Note: although sed does have a nicer regex syntax with -r, it is a non-portable GNU-ism and thus doesn't work on MacOS, BSD, or Solaris.

Quick Guide

  1. String-literal mode. By default, expressions are treated as regex. Use -s or --string-mode to disable regex.
> echo 'lots((([]))) of special chars' | sd -s '((([])))' ''
lots of special chars
  1. Basic regex use - let's trim some trailing whitespace
> echo 'lorem ipsum 23   ' | sd '\s+$' ''
lorem ipsum 23
  1. Capture groups

Indexed capture groups:

> echo 'cargo +nightly watch' | sd '(\w+)\s+\+(\w+)\s+(\w+)' 'cmd: $1, channel: $2, subcmd: $3'
cmd: cargo, channel: nightly, subcmd: watch

Named capture groups:

> echo "123.45" | sd '(?P<dollars>\d+)\.(?P<cents>\d+)' '$dollars dollars and $cents cents'
123 dollars and 45 cents

In the unlikely case you stumble upon ambiguities, resolve them by using ${var} instead of $var. Here's an example:

> echo '123.45' | sd '(?P<dollars>\d+)\.(?P<cents>\d+)' '$dollars_dollars and $cents_cents'
 and 
> echo '123.45' | sd '(?P<dollars>\d+)\.(?P<cents>\d+)' '${dollars}_dollars and ${cents}_cents'
123_dollars and 45_cents
  1. Find & replace in a file
> sd 'window.fetch' 'fetch' -i http.js

That's it. The file is modified in-place.

To do a dry run, just use stdin/stdout:

> sd 'window.fetch' 'fetch' < http.js 
  1. Find & replace across project

Good ol' unix philosophy to the rescue.

fd -t f --exec sd 'from "react"' 'from "preact"' -i {}

Same, but with backups (consider version control).

for file in $(fd -t f); do
  cp "$file" "$file.bk"
  sd 'from "react"' 'from "preact"' -i "$file"; 
done