From 6ac87031e97b4375a2ae525d172c88def517e392 Mon Sep 17 00:00:00 2001 From: Tom Ryder Date: Mon, 8 Aug 2016 10:41:32 +1200 Subject: Be more specific about shell script compatibility --- README.markdown | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'README.markdown') diff --git a/README.markdown b/README.markdown index a9e411fd..e2a07af3 100644 --- a/README.markdown +++ b/README.markdown @@ -92,9 +92,9 @@ configuration isn't too distant from the defaults. ### Shell -My `.profile` and other files in `sh` are written in Bourne/POSIX shell script, -so they should work in most `sh(1)` implementations. Individual scripts called -by `.profile` are saved in `.profile.d` and iterated on login for ease of +My `.profile` and other files in `sh` are written in POSIX shell script, so +they should work in most `sh(1)` implementations. Individual scripts called by +`.profile` are saved in `.profile.d` and iterated on login for ease of management. All of these boil down to exporting variables appropriate to the system and the software it has available. @@ -274,11 +274,11 @@ loaded using @tpope's [pathogen.vim](https://github.com/tpope/vim-pathogen). Scripts ------- -Where practical, I make short scripts into POSIX-compatible `sh(1)`, `awk(1)`, -or `sed(1)` scripts in `~/.local/bin`. A few of them still have Bashisms for -various reasons. I try to use shell functions only when I actually need to, -which tends to be when I need to tinker with the namespace of the user's -current shell. +Where practical, I make short scripts into POSIX (but not Bourne) `sh(1)`, +`awk(1)`, or `sed(1)` scripts in `~/.local/bin`. A few of them still have +Bashisms for various reasons. I try to use shell functions only when I actually +need to, which tends to be when I need to tinker with the namespace of the +user's current shell. Installed by the `install-bin` target: -- cgit v1.2.3