aboutsummaryrefslogtreecommitdiff
path: root/README.markdown
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2016-08-20 12:43:58 +1200
committerTom Ryder <tom@sanctum.geek.nz>2016-08-20 12:43:58 +1200
commit8230f0a0ee64cc7c1e2538fd65403ffdc4a8bd8e (patch)
treec29a4d4f6b0f84d8cc8dc0e55c543e2444373038 /README.markdown
parentAdd an issue (diff)
downloaddotfiles-8230f0a0ee64cc7c1e2538fd65403ffdc4a8bd8e.tar.gz
dotfiles-8230f0a0ee64cc7c1e2538fd65403ffdc4a8bd8e.zip
Move bd() from Bash func section in README
Diffstat (limited to 'README.markdown')
-rw-r--r--README.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.markdown b/README.markdown
index 6e6f2bbb..b3f2396b 100644
--- a/README.markdown
+++ b/README.markdown
@@ -164,6 +164,7 @@ If a function can be written in POSIX `sh` without too much hackery, I put it
in `sh/shrc.d` to be loaded by any POSIX interactive shell. Those include:
* `bc()` silences startup messages from GNU `bc(1)`.
+* `bd()` changes into a named ancestor of the current directory.
* `diff()` forces the unified format for `diff(1)`.
* `cd()` wraps the `cd` builtin to allow for a second parameter for string
substitution, emulating a Zsh function I like.
@@ -194,7 +195,6 @@ in `sh/shrc.d` to be loaded by any POSIX interactive shell. Those include:
There are a few other little tricks defined for other shells, mostly in
`bash/bashrc.d`:
-* `bd()` changes into a named ancestor of the current directory.
* `fnl()` runs a command and saves its output and error into temporary files,
defining variables with the filenames in them.
* `grep()` tries to apply color and other options good for interactive use,