aboutsummaryrefslogtreecommitdiff
path: root/README.markdown
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2016-08-21 10:29:11 +1200
committerTom Ryder <tom@sanctum.geek.nz>2016-08-21 10:29:11 +1200
commite4e57cc558448d131b2f7fdb5580cbf323b036d2 (patch)
tree10f4149b93ec49cfbdcf36d1631006abd725a362 /README.markdown
parentAdd --devices and --directories to grep(1) opts (diff)
downloaddotfiles-e4e57cc558448d131b2f7fdb5580cbf323b036d2.tar.gz
dotfiles-e4e57cc558448d131b2f7fdb5580cbf323b036d2.zip
Update to new shell script policy
Diffstat (limited to 'README.markdown')
-rw-r--r--README.markdown11
1 files changed, 5 insertions, 6 deletions
diff --git a/README.markdown b/README.markdown
index 4108914d..d9e2567d 100644
--- a/README.markdown
+++ b/README.markdown
@@ -98,14 +98,13 @@ they should work in most `sh(1)` implementations. Individual scripts called by
management. All of these boil down to exporting variables appropriate to the
system and the software it has available.
+I make an effort to target POSIX for my functions and scripts where I can, but
+Bash is my interactive shell of choice.
+
My `.bash_profile` calls `.profile`, and then `.bashrc`, which only applies for
interactive shells. Subscripts for `.bashrc` are loaded from `.bashrc.d`. The
-contents of the two directories changes depending on the host, so only specific
-scripts in it are versioned.
-
-My interactive and scripting shell of choice is Bash; as a GNU/Linux admin who
-ends up installing Bash on \*BSD machines anyway, I very rarely have to write
-Bourne-compatible scripts, so all of these files are replete with Bashisms.
+contents of the `*.d` directories changes depending on the host, so only
+specific scripts in it are versioned.
As I occasionally have work on very old internal systems, my Bash is written to
work with [any version 2.05a or